Chat now with support
Tchattez avec un ingénieur du support

Defender 5.9.5 - Defender AD FS Adapter 5.10 Release Notes

Release Notes

One Identity Defender AD FS Adapter 5.10

Release Notes

November 2019

This release notes provide information about Defender AD FS Adapter release.

About One Identity Defender AD FS Adapter

Resolved issues

Known issues

System requirements

Getting started with One Identity Defender AD FS Adapter

About One Identity Defender AD FS Adapter

About One Identity Defender AD FS Adapter

Defender AD FS Adapter integrates with Microsoft Active Directory Federation Services (AD FS) 3.0 and 4.0 to add two-factor authentication to services using browser-based federated logins. Defender AD FS Adapter supports relying parties that use Microsoft WS-Federation protocol, like Office 365, as well as SAML 2.0 federated logons for cloud apps like Google Apps and salesforce.com.

Resolved issues

The following is a list of issues addressed in this release.

Table 1: General resolved issues
Resolved Issue Issue ID
SMTP domains are not supported by Defender AD FS Adapter. 79900

Known Issues

The following is a list of issues known to exist at the time of release.

 

Table 2: Known issues

Known issue

Issue ID

When a user using their GrIDsure token authenticates using the Defender ADFS Adapter, they are unable to reset the PIP. This can happen if the user has other tokens assigned to them besides the GrIDsure token.

Workaround: Make sure that no other tokens are assigned to the user, if they are using the GrIDsure token for authentication.

21334

When a user tries to authenticate using the Defender ADFS Adapter, they may get an ambiguous error “Access denied - no valid route found.” This error may appear if the user does not have any Defender tokens assigned to them.

Workaround: Make sure that the user in question has a Defender token assigned.

21146

When a user tries to authenticate using the Defender ADFS Adapter, they may get the error “Incorrect user ID or password. Type the correct user ID and password, and try again.”, even though they are entering a correct username and password. This may occur if the security policy set up in Defender is preventing the user to log in at this time.

Workaround: Check the security policy for the access node in question to make sure that the problem is, in fact, that the login policy is preventing the user to log in at this time.

5258

Outils libre-service
Base de connaissances
Notifications et alertes
Support produits
Téléchargements de logiciels
Documentation technique
Forums utilisateurs
Didacticiels vidéo
RSS Feed
Nous contacter
Obtenir une assistance en matière de licence
Support Technique
Afficher tout
Documents connexes