Strong Authentication using IBM Security Verify APIs
IBM Security Verify Access (ISAM) uses IBM Security Verify APIs to invoke authentication mechanisms for multi-factor authentication. This option configures a set of Advanced Access Control (AAC) mechanisms in ISAM to call authentication and user self care APIs in the IBM Security Verify subscription. Users need only ever access ISAM directly and AAC policy can be used to handle all aspects of the user authentication and self care experiences without any external re-directions to cloud. The integration between Advanced Access Control and IBM Security Verify is achieved using JavaScript mapping rules and can be further extended or customized beyond this wizard. See Cloud Identity API Integration. For this procedure, the Local Management Interface and web browser communicates with IBM Security Verify.
- Ensure the IBM Security Verify host can be resolved and contacted by the Local Management Interface. See Configure DNS.
- If a proxy is required to reach IBM Security Verify Access, ensure it is configured on the Administrator Settings page.
At runtime, the Advanced Access Control runtime and client web browser communicates with IBM Security Verify.
- Create a connection
- Removing a connection
- Manually creating a connection
- Manually removing a connection
Parent topic: IBM Security Verify