Aaron, The user.unityid field should not contain the affailiation. However, it can contain an @ in it. We did this because of a custom account system here at NCSU that uses email addresses in the unityid field. However, those addresses all have the same affiliation associated with them. This results in a unityid@affiliation like
[email protected]@ITECS which is a little strange, but it worked out okay. The one issue it did cause was requiring that only the part before the first @ be used as the user account in reserved systems. As an aside, the reason the field is named 'unityid' instead of something like 'userid' is because that's what we call them here at NCSU. By the time we moved to ASF, we didn't feel like it was worth all the code changes to rename it when no end users would see it. I hope that clarifies things. Josh On 08/14/12 15:13, Aaron Coburn wrote: > Hi, Guys, Is the user.unityid value supposed to have an affiliation > value attached to it? That is, should it be in this format: > user@affiliation? None of the users in our system have an affiliation > value in that field, yet in utils.php:updateRequest(), it seems that > the call to getUserlistID($user['unityid']) expects it in the > user@affiliation format. > > It causes extension requests to fail. It is easy to fix, but I want > to make sure I understand this properly. > > Aaron > > > -- Aaron Coburn Systems Administrator and Programmer Academic > Technology Services, Amherst College > [email protected]<mailto:[email protected]> -- ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
