View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 2115 | RackTables | default | public | 2026-06-17 03:01 | 2026-07-09 19:26 |
| Reporter | sauron | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 0.22.0 | ||||
| Summary | 2115: Please support special characters in RackCode (so an email address can be used as a UserID) | ||||
| Description | As mentioned - it would be great to support special characters in RackCode - at leasy as far as the @ symbol, as is common to attempt to use an email address as a username. Alternatively - at leat support a method of mapping an email address to a username. My use case here is that the username is externally provided by the web server extracting a rfc822 email address from a presented client certificate, so there's little opportunity to alter it, and it would be very nice to have racktables trust the httpd provided username. | ||||
| Steps To Reproduce | Attempt to add anything of the form "allow {$username_foo@bar.com} and it fails to verify. | ||||
| Tags | No tags attached. | ||||
|
Using an e-mail address as a username is indeed a sound use case in general, but it is not immediately clear whether changing the RackCode syntax will have any immediate or delayed unwanted side effects. Is the "@bar" part the same in all usernames? If yes, and if the "foo" part is exactly one of the X.509 certificate fields, it may be simpler to configure the HTTP server to set the ''REMOTE_USER'' environment variable to the "foo" part only. Specifically for Apache httpd this would mean: https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslusername https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#authbasicfake https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#ssloptions Without any knowledge of your configuration and the X.509 certificate structure, the best guess I could make is that the "foo" could be the CN, then ''SSLUserName SSL_CLIENT_S_DN_CN'' would strip the domain part. Please ask your X.509 administrator whether this makes sense and is implementable. |
|
| "The email account that you tried to reach does not exist." | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-06-17 03:01 | sauron | New Issue | |
| 2026-07-09 18:54 | infrastation | Note Added: 0004607 | |
| 2026-07-09 19:26 | infrastation | Note Added: 0004609 |