OK, thanks again, and I do understand how to use the custom scim attributes now. However, you are not understanding my initial issue/question. If you do a search on Gluu users from the admin gui, you will see that there is an attribute displayed in the results with a display name of "Email". That is populated by the ldap GluuPerson "mail" attribute. I expected to be able to create a user with the SCIM API and have the email show up there, but since the SCIM Email populates "oxTrustEmail" instead of GluuPerson.mail, you have not provided a way to populate the email displayed in the User search from the SCIM Client API. Hence the confusion. We need to use an email address as an alternate login, by adding a custom basic authentication script, which is why I have been asking. We can create and populate our own custom attribute, which will be fine, but seemed unnecessary since you seem to have two places for email already, or we could use the oxTrustEmail attribute, but then we have the added complexity of looking up a user within the script by their oxTrustEmail primary email, which will involve parsing the json that attribute is stored in in the ldap database.
Thanks,
Carl