Jun 22 2017
11:20 AM
- last edited on
Jan 14 2022
04:49 PM
by
TechCommunityAP
Jun 22 2017
11:20 AM
- last edited on
Jan 14 2022
04:49 PM
by
TechCommunityAP
Hi
First I'd like to confirm my understanding that the passwords for invited guests are managed in the guest/partner's own identity provider and not in our (resource provider) AAD tenant?
I'd also like to confirm if at any time the guest password is actually copied to or stored in our AAD tenant for the purpose of credential authentication. I assume that AAD B2B uses pass-through authentication to the guest's identity provider, but need to confirm the guest passwords never leave the guest's identity provider.
Second-lastly the question was raised in another question about password resets, but unanswered, and that is if we use AAD B2B Collaboration and our guest's have their own identity provider, can we apply any form of password rules on our side regarding password length, complexity or expiry?
And lastly, I'd like to know if there is any user/technical documentation regarding SSPR process as outlined in the discussion about password resets?
Thanks and take care,
Shayne
Jul 06 2017 08:11 AM
SolutionHi Shayne-
B2B by default uses federated authentication. So that the guest passwords never leave the partner org. Also, the password policies are managed by the partner org.
The resource organization (the one that has invited the partner user into their directory) - can enable MFA for the B2B users inorder to increase the identity proof of the partner user signing in.
Password resets also happen in the partner organization. I responded in the thread you have referenced, but pasting my response here for your convenience:
Here are the details about SSPR for the B2B user that is invited to a resource tenancy from their identity tenancy:
SSPR for B2B users in the context of the resource tenancy will be blocked.
Hope this helps.
Please try this out and let us know if you have any issues!
Jul 06 2017 08:11 AM
SolutionHi Shayne-
B2B by default uses federated authentication. So that the guest passwords never leave the partner org. Also, the password policies are managed by the partner org.
The resource organization (the one that has invited the partner user into their directory) - can enable MFA for the B2B users inorder to increase the identity proof of the partner user signing in.
Password resets also happen in the partner organization. I responded in the thread you have referenced, but pasting my response here for your convenience:
Here are the details about SSPR for the B2B user that is invited to a resource tenancy from their identity tenancy:
SSPR for B2B users in the context of the resource tenancy will be blocked.
Hope this helps.
Please try this out and let us know if you have any issues!