r/sysadmin • u/gopherwasbetter • 9h ago
Question Displaying User Credentials
Azure hybrid environment here. We currently append user email signatures via a transport rule. Looking at CodeTwo, but I still think I'll have to solve this problem.
Some users have professional credentials they want to list after their name. In the past, the handful of people we had, we just added it to the display name, which is kind of clumsy. We can continue with that I suppose, but I wonder if there's a better way (like, . Side note, how do you handle, if at all, credentials that require a trademark symbol?
I could add these as attributes and format them in the transport rule, but I'm wondering what other ways people are doing this...
•
u/Randalldeflagg 9h ago
you can put them as one of the 15 optional attributes. We use 1 for booking links. helpdesk puts the link into the attribute, then we set that attribute as an option in CodeTwo. Keeps the address book neat and uniform but still gives the user the options they as for.
Or you can even make it an optional field with in CodeTwo where they can add their own things there. (HR approved this for about 3 hours until people started putting really dumb things in there)
•
u/Vetka3000 9h ago
One caveat here. Exchange Online transport rules can match "CustomAttribute1-15", but native disclaimer templates can't interpolate them as placeholders.
CodeTwo supports synced "extensionAttribute" values via Entra Connect, so I'd store the designation (including ®/™) there and leave "displayName" untouched. Just make sure those attributes are actually syncing.
•
u/Frothyleet 7h ago edited 7h ago
Code 2 or its competitors will let you use whatever Entra fields you want in the signature templates. You'd just pick an Entra field that you are not otherwise using, put it after the "display name" field in the template, and users who have something to populate that field will get it added to their signature.
Side note, how do you handle, if at all, credentials that require a trademark symbol?
It's a unicode character. You handle it the way you handle any character, usually. Most modern authentication systems will happily accept whatever unicode you like (yes you can have a poop emoji in a hostname). The only limitation I guess would be the HID side of things. If someone wants it as part of their username or password they'll probably need to remember alt+0153
•
u/BWMerlin 4h ago
CodeTwo has an inbuilt feature that allows users to edit certain parts of the email signature that you specify.
Basically it allows editing the extended attribute values and you can choose if those values are written back to Entra or if you want CodeTwo to cache the users modifications and not overwrite them on next sync.
•
u/alphageek8 Jack of All Trades 3h ago
We use an extension attribute that holds the employee's accreditation(s).
The actual source comes from our HR system and goes through an automation to parse out and map the clean version of the accrediation into the signature. We also do some ordering because there's a couple accreditations that should show up first if there's multiple.
•
u/GasBackground3335 9h ago
may be janky but in for that I used fax.... which is janky but when the hell are you using the fax field in ad?
•
u/InsolentJaguar 9h ago
We've always used attributes fields to do things like pronouns for certain companies that want them displayed, or professional creds.
Easy to map in Code2, and easy in AD.