Authentication
Last updated
Last updated
Configure the authentication method best for your business. You can use Windows, SAML 2 or ADFS to authenticate Aiimi Insight Engine. There are also some additional authentication security features that can be used in dev or test environments.
Use Windows Authentication to authenticate objects, services and users. It will help verify how genuine an object is and for services and people that the credentials are authentic.
Check Windows Authentication to use Windows Authentication.
SAML2 is an open standard that allows single sign-on (SSO) of applications. It is used to authenticate a user and allow them to gain access to Aiimi Insight Engine.
SAML 2 Authentication - If checked SAML2 will be used for Aiimi Insight Engines Authentication.
Application identifier - Enter the identifier of the Application in the identity provider.
Issuer - Enter the issuer of the Identity Provider.
Sign On URL - Enter the endpoint URL for signing in to the authenticator.
Logout URL - Enter the endpoint URL for logging out of the authenticator.
App URL - Enter the endpoint for Aiimi Insight Engine Search application that will complete the login.
Use {0} as a placeholder for the host and port to access the API.
Signature Validation Certificate - Enter the filepath for the public certificate used to validate token signatures.
Aiimi Insight Engine supports ADFS for single sign on. A private key needs to be generated and network changes are required before ADFS is enabled. The copy of the certificate will need to be added to each server running IIS and hosting Aiimi insight Engine.
Check Enable ADFS Authentication use ADFS.
ADFS URL - Enter the ADFS URL.
Redirect URL - Enter your Redirect URL.
Certificate Path - Enter the path to the certificate/private key.
Certificate Password - Enter the password for your certificate.
These setting impact the safety, security and integrity if your system. Proceed with caution.
Get information about your APIs during development and testing. This exposes your API details and should only be enabled in dev or test environments. To use Swaggers inbuilt testing the Bearer Token Authentication must be enabled.
Allow tokens to be stored in an auth header not just HTTP. This increases your security risk and should only be enabled in dev or test environments. This must be enabled to use Swaggers inbuilt testing.
If enabled, logged out tokens will only be invalidated upon expiry. This is only recommended for dev or test environments.
