Zum Hauptinhalt springen
Diese Seite ist nur auf Englisch verfügbar. Englische Seite öffnen

ADFS auto-creation of authenticated users

The platform can create authenticated users automatically the first time they sign in via SSOSSO Ein Authentifizierungsverfahren, bei dem sich Benutzer einmal bei einem Identitätsanbieter anmelden und dann auf Process360 Live zugreifen, ohne ihre Anmeldedaten erneut einzugeben., so you don't have to add them by hand first. These steps cover the on-premises SAML2-with-ADFS specifics — discovering the attribute names ADFS sends and restarting the service; with adjustments they apply to other identity providers. For cloud, see Auto-create users on first sign-in.

When auto-creation is configured, an authenticated user not yet in the platform's user table is created during sign-in, and a corresponding entry appears in Administration → User Management. If the user already exists, the existing user is matched. New users are placed in the Users group — add that group first, and give it a default role, or auto-created users get no permissions and may see a permission message.

Prerequisites​

  • A working SAML2 ADFS setup.
  • The Users group created in the platform, with an appropriate default role.

Steps​

  1. Complete the Microsoft ADFS Server setup.

  2. In Administration → User Management → SAMLSAML Ein XML-basierter Standard für den Austausch von Authentifizierungs- und Autorisierungsdaten zwischen einem Identitätsanbieter und einem Dienstanbieter. Process360 Live unterstützt SAML 2.0 für SSO., select Automatically create authenticated users to enable it.

  3. Determine the SAMLSAML Ein XML-basierter Standard für den Austausch von Authentifizierungs- und Autorisierungsdaten zwischen einem Identitätsanbieter und einem Dienstanbieter. Process360 Live unterstützt SAML 2.0 für SSO. attribute names (claim type URIs) ADFS sends for first name, last name, and email — directly or indirectly. A claim type URI is the standard identifier for an attribute, such as http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname; on the ADFS side, a claim rule issues these from your directory.

    • Direct — ask your ADFS team for the claim type URIs. On the ADFS side they're issued by a claim rule set on the Edit Rule → LDAP Attribute tab.

      Entering the LDAP attribute claim rule in ADFS.

      The resulting ADFS claim rule looks like:

      c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"]=> issue(store = "Active Directory", types = ("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname", "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress", "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"), query = ";sAMAccountName,givenName,mail,sn;{0}", param = c.Value);
    • Indirect — read the attribute names from the platform's logs. In Administration → Support → Logging Settings, set DEBUG, disable Log All Classes, select Custom, and enter org.springframework.security.saml2;org.opensaml;PROTOCOL_MESSAGE — on versions before 20.0.0, use org.springframework.security.saml in place of org.springframework.security.saml2. Have a user sign in, then read the assertion in the System Log. If you can't find the attribute names, they may be encrypted — use the direct method. An example assertion:

      <Subject><NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">user@igrafx.com</NameID>
      <SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
      <SubjectConfirmationData InResponseTo="aba86j6216if75f4g52jfidjf0ddej" NotOnOrAfter="2018-02-06T15:58:42.048Z" Recipient="https://www.igrafx.com:443/saml/SSO"/>
      </SubjectConfirmation>
      </Subject>
      <AttributeStatement>
      <Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"><AttributeValue>LastName</AttributeValue></Attribute>
      <Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname"><AttributeValue>FirstName</AttributeValue></Attribute>
      </AttributeStatement>
  4. In Administration → User Management → SAMLSAML Ein XML-basierter Standard für den Austausch von Authentifizierungs- und Autorisierungsdaten zwischen einem Identitätsanbieter und einem Dienstanbieter. Process360 Live unterstützt SAML 2.0 für SSO., enter the claim type URIs for each attribute:

    First name http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
    Last name http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
    Email http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
  5. Restart the service.