Then you should to edit the LDAP IWDS settings tab to associate the login 2 field with the value "userprincipalname".
Optional: the login 2 field is supported from IWDS 2.4. Enter the UPN value in the “login 2 field” of user properties. “login 2”: the inWebo User emails must match the Azure AD UPN. Option 2 (if option 1 is not possible): Use another inWebo login type (login 2 or user email) If it is still possible and without impact, we recommend that you change the format of your inWebo users logins to match the Azure AD UPN. Option 1: Change the format of the inWebo users logins If the inWebo user logins do not match the Azure AD UPN: If the inWebo user logins match the Azure AD UPN, we suggest you to choose "login type= user login".
The login type value must match the Azure AD UPN value. To communicate with inWebo, this requires the inWebo user logins to be in UPN format (e.g. Login Type → Select the login type to use during Azure AD user authentication process: user login, login 2 and user email.Īzure AD uses the UPN (UserPrincipalName) attribute as a login for the authentication process. It allows the junction between the inWebo connector and the Azure AD custom control (when creating the custom control, the ClientID is mentioned in the JSON code). The name of the connector will be used to create the secure site, so it will appear in the authentication context sentence.Ĭlient ID → Enter the client ID. Step 1: Creating a new inWebo Azure AD connectorĬonnect as administrator to the inWebo administration console.Ĭhoose to create a connector of type “OIDC Azure AD”.įill in the fields to create your inWebo Azure AD Connector:Ĭonnector name → Enter a chosen name / information to define the connector's goal in the administration console. Please be careful when choosing the inWebo login to use for the exchange with Azure AD (see “Login type” parameter below). Azure AD uses the UPN (UserPrincipalName) attribute as a login for the authentication process.
0 kommentar(er)
