try 

headers = 'X-No-WWW-Authenticate'


On Wednesday, July 1, 2015 at 6:12:56 PM UTC+5:30, Dustin wrote:
>
> Hello,
>
> I built a Web-App with AngularJS (1.3) which is connected to a 
> PHP-REST-api (Slim Framework). Now I've got a feature request to implement 
> optional Single-Sign-On, which means the App should try to authenticate 
> using SSO and if that does not work it should display the usual login 
> dialog.
>
> So my idea was to implement a new api-route */api/sso* which is requested 
> by the app before displaying the login dialog. If the sso authentication 
> worked then the App should redirect directly to the main view, if not then 
> it should display the login dialog. This is working quite well if the 
> browser is properly configured to do SSO, but if not it displays two login 
> dialogs: 
>
>    - one from the browser because if SSO is not working the server sends 
>    back an negotiate-header (WWW-Authenticate:Negotiate) 
>    - the usual App login dialog 
>
> My question is: can I somehow prevent the browser login dialog that is 
> caused by the failed SSO-authentication? On the server side the SSO-part is 
> implemented with mod_auth_kerb in apache2.4.
>
> Or is there an other way to do optional SSO? The goal is that if a user 
> opens the Web-App on a device where he is logged in on our Active Directory 
> and the browser is configured to do SSO then he should directly see the 
> main view and if not he should see the Web-App's login dialog, but never 
> the browser's login dialog.
>
> Thanks in advance for your help!
>
> Regards
> Dustin
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to