In addition to username and password, you can collect additional attributes from users, such as a users email address or job title.
To collect additional attributes
Note: If you expect the additional attributes or the Password to contain special characters (" . & = + ? ; / : @ = , $ %), you need to URL-encode each namespace in the .fcc file.
To modify the .fcc file, add the following line at the beginning of the file:
@password=PASSWORD=%PASSWORD%&newattr1=%newattr1%&newattr2=%newattr2%
If the additional attributes have special characters, the line should look like the following:
@password=PASSWORD=%urlencode(PASSWORD)%&newattr1%=%urlencode(newattr1)%&newattr2=%urlencode(newattr2)%
where newattr1=%newattr1%and newattr2=%newattr2% represent the additional attributes. The value before the equals sign is the attribute name and the value between the percent sign (%) sign is the attribute value.
The FCC parses the names of the new attributes from the attribute values.
Note: Append additional attributes to the @password directive with the ampersand (&) character.
When you add attributes to the FCC, keep the following in mind:
@password=PASSWORD=%PASSWORD%&mail=%address%
or
@password=PASSWORD=%urlencode(PASSWORD)%&mail=%urlencode(address)%
you would add a line to the .fcc file similar to the following:
<input name="address" type="text">
@password=PASSWORD=%PASSWORD%&mail=%address%
or
@password=PASSWORD=%urlencode(PASSWORD)%&mail=%urlencode(address)%
where mail is the name of the LDAP attribute that stores email addresses.
For example, to add the attribute mail (from the example above) to the authentication scheme, enter the following in the Additional Attributes List field:
AL=PASSWORD,mail
Note: The additional attribute names are case-sensitive.
Copyright © 2010 CA. All rights reserved. | Email CA about this topic |