ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.
This website uses cookies. By continuing to browse or login to this website, you consent to the use of cookies. Learn more.
OK
jlrodriguez
Vice Admiral
Vice Admiral
‎2019-10-24 20:53
395 views

Azure AD Windows 10 login

Jump to solution

Hi,

 

Can anyone confirm if the following scenario can work with NAM?:

An Azure AD Domain federated with WS-Trust with NAM with the corporate directory (eDir). A workstation is registered in this Azure AD Domain. The user login into the workstation using their credentials "mail address" and password of the corporate directory (eDir).

The AD environment is NOT a hybrid OnPremises AD and Azure AD.

 

Regards

Jose Luis

Labels (3)
Labels
0 Likes
Report Inappropriate Content
1 Solution

Accepted Solutions
Gireesh
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
‎2019-10-29 15:30

Jump to solution

Yes, this scenario should work.

There's an issue when the metadata is larger than 64KB though https://support.microfocus.com/kb/doc.php?id=7022822

Even though the TID discuss the Hybrid scenario, this applies to non-hybrid cases as well.

View solution in original post

Report Inappropriate Content
2 Replies
Gireesh
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
‎2019-10-29 15:30

Jump to solution

Yes, this scenario should work.

There's an issue when the metadata is larger than 64KB though https://support.microfocus.com/kb/doc.php?id=7022822

Even though the TID discuss the Hybrid scenario, this applies to non-hybrid cases as well.

View solution in original post

Report Inappropriate Content
jlrodriguez
Vice Admiral
Vice Admiral
‎2019-10-29 22:42

Jump to solution
Thanks!!  Applying this TID solved it!

Regards

0 Likes
Report Inappropriate Content
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.