...
Field (field name is user-selectable) | Azure Attribute Name (capitalization must be exact) | |
|---|---|---|
1 | ||
2 | legal first name | LegalFirstName |
3 | legal last name | LegalLastName |
4 | display name (preferred name) | DisplayName |
5 | netid | username |
6 | active primary affiliation | SyrEduActivePrimaryAffiliation |
7 | title | JobTitle |
8 | department | Department |
9 | department number | DepartmentNumber |
10 | education level (class) | SyrEduLevel |
1011 | educational program | SyrEduProgram |
1112 | OU (from enterprise directory) | SyrEduUnitCode |
13 | SUID | SyrEduSUID |
To collect that information so it can be saved with a survey submission or displayed on the screen to a user filling out the form, you need to create Embedded Data variables to hold the information. This is done right within the Authenticator block currently on the screen. The variable name you want to create is on the left (and can be any name you choose) and the name of the Shibboleth parameter is listed on the left. A sample Authenticator block with the correct options selected and all the possible values collected is shown below:
In order for the login to be required before filling out the form, the Authenticator block needs to be the first thing in the flow so after filling in the information in that block as above, click on the Move link in the bottom of the block and drag the Authenticator block to the top of the flow
Blocks that display surveys should be indented after Branch on Successful Authentication. This way the survey is only displayed if the authentication succeeded (see below)
...