• Microsoft Active Directory via the LDAP standard (authentication only, no Single Sign On).
• Microsoft Azure via the LDAPS standard (authentication only, no Single Sign On).
• Federated Single Sign On via the SAML 2.0 standard (Vendor neutral, including Active Directory).
• Federated Single Sign On via the OpenID Connect standard (Vendor neutral, including Active Directory).
• Google Accounts via Google's proprietary authentication module

1. Open in a new private browser window (to avoid possible cookie issues): 

• https://[your library tenant].concordinfiniti.com/login
• You may have to request this page twice if you have SAML 2.0 turned on

2. Enter your username as recorded for the user profile you are authenticating with. This may differ from your username in other school systems. 

• If you do not know your username and no other librarian has access, please inform Concord Support so we can check who has a librarian administration account.

3. Enter your password as recorded in Infiniti/LibPaths. This may differ from your password in other school systems. 

• If you do not know your password and your email address has been recorded in your Infiniti account, you can use the "I cannot login" > "Reset your password" action from the login page. 
• If you do not have an email address recorded to your Infiniti account, inform Concord Support so we can either assign an email address or generate a temporary password for you.
• If you do not have an account in Infiniti and no other administrative user is able to create one for you, please inform Concord Support and we can create one for you if you are entitled to administrative access.

4. Once an administrative library manager has access to Infiniti/LibPaths through this login page, the library manager can create or repair other library manager or IT Team accounts in SETTINGS > Users.

• Reviewing or (re)configuring Remote Authentication modules may also require administrative access to Infiniti/LibPaths by your IT Team with technical knowledge and experience of the relevant remote authentication protocol.

1. connectivity,
2. configuration of the local ecology, or
3. propagation issues

• Check if the hostname, port and directory domains are correct.
• Check that Infiniti has access through relevant firewalls.
• If encrypted LDAP is being used (Strongly Recommended), check that LDAPS is correctly configured for your Active Directory server or Azure cloud service.
• Connectivity be tested with the "Test Connectivity" link on the Infiniti configuration screen for LDAP.

• Your school's IT staff or contractors must configure and maintain a Google administrator or developer account to act as the school's configuration of Infiniti to be seen by Google as an "application" in your school ecology.
• Only users with a Google Account authorised by your school's IT configuration can use this sign-in method. Only users that have agreed (a Google dialogue prompt) to link their Google and Infiniti accounts are able to login with this sign-in method.
• As a proprietary protocol, Google reserves the right to alter the nature of this authentication and who and how it can be accessed. Schools using this remote authentication option are recommended to have a fallback option.

• Your IT Team must configure and maintain a service provider (vendor terminology may differ) for Infiniti/LibPaths, declared within your authentication server or service's administrative portal. The method of doing so:
• will differ by vendor
• is documented differently by each vendor, and
• your IT Team is expected to familiarise themselves with the relevant vendor's documentation, connectivity, and (potential) subscription requirements.
• If your library has turned on this module as the "Default Authentication Method", we strongly advise that you switch off this module as the default until you resolve any underlying connectivity or configuration problems. However, doing so will rely on users (library managers, staff, or students) being able to access Infiniti through other authentication methods, e.g., manually with user ID and Password.
• If Infiniti/LibPaths cannot re-populate authentication server (identity provider) metadata from the declared "Discovery URL", this module can fail when the authentication server's behaviour changes. The URL's suitability for Infiniti/LibPaths and its availability should be reviewed by your IT Team.

Go to: Administrative Settings > Integrations > SAML 2.0

• SAML 2.0 relies on the sharing of configuration metadata between Infiniti (as a Service Provider) and the authentication service (as an Identity Provider). Most problems with using SAML 2.0 for remote authentication are a result of incorrect configuration or an inability for either Infiniti/LibPaths or the authentication service to load or propagate their required metadata. 
• Once correctly configured, your service provider (Infiniti/LibPaths) and identity provider (vendor) behaviour will take time to propagate. How long will differ by vendor, but we recommend at least one hour between each re-configuration you believe to be correct.
• If you have turned on this module as the "Default Authentication Method", we strongly advise that you switch off this module as the default until you resolve any underlying connectivity or configuration problems. However, doing so will rely on users (library managers, staff, or students) being able to access Infiniti through other authentication methods, e.g., manually with user ID and Password.
• button at the bottom of the Infiniti/LibPaths SAML 2.0 configuration page will give more information about how Infiniti/LibPaths uses SAML 2.0, how Infiniti/LibPaths configures SAML 2.0, and common problem resolution scenarios. This includes specific information on Azure.
• SAML 2.0 is a technical protocol and documentation and advice on SAML 2.0 is targeted to the IT Team and contractors with sufficient prior familiarity with the SAML 2.0 protocol and their chosen authentication vendor's documentation and quirks.

1. A duly authorised IT Team member or contractor with knowledge of your network ecology is the primary participant in the meeting.
2. The representative(s) have access to both their authentication service and Infiniti with administrative privileges.
3. The session uses a widely supported webinar platform, e.g., Zoom or MS Teams, agreed upon prior to the meeting; with the ability to share the screen with your IT Team representative(s). We do not require remote control, but general screen visibility of vendor configuration or tools can greatly improve the diagnostic process. By default, we offer webinar/video sessions through Zoom.
4. Meeting time and participants are propagated by email.

1. A test username and password that Concord Support can use to test/reproduce the issue.
2. The precise time an error occurred with your test user. 
3. A full high resolution snapshot of the error that occurred.
4. In the case of SAML 2.0, either the Identity Provider URL declared in Infiniti/LibPaths or the Identity Provider file uploaded; whichever is toggled.