You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.
I would like to know if you will support WAAD as primary authentication system and also authentication with other social identity providers (I mean to display the “login page” of WAAD at the left side of the screen and to continue displaying the other IP buttons).
Thanks in advance.
The text was updated successfully, but these errors were encountered:
No - the "left side of the screen" will be local logins. I don't even think that you can embed the WAAD login screen (that would be a security problem) - but we will support WAAD as an identity provider (either via ws-fed or openid).
oh. I was thinking in a scenario where a "cloud" application hosted in azure uses WAAD to do the login.... but it also allows to login using other IPs.
The idea was to show the WAAD login screen inside an IFRAME. Do you consider it a security problema?
If the primary IdP is WAAD, it would be WAAD's job to allow 3rd party logins ;)
Typically you would not allow an third party to load the login/consent screens in an iframe since this enables click jacking attacks. I assume WAAD would not allow this.
I would like to know if you will support WAAD as primary authentication system and also authentication with other social identity providers (I mean to display the “login page” of WAAD at the left side of the screen and to continue displaying the other IP buttons).
Thanks in advance.
The text was updated successfully, but these errors were encountered: