Re: AW: Suppress or replace WWW-Authorization header

2015-10-29 Thread Christopher Schultz
Chris, On 10/29/15 5:12 AM, chris derham wrote: >>> Torsten, >>> >>> Add an interceptor to AngularJS to detect the 401 and do whatever you >>> want, e.g. redirect to a login page. Then when you have the >>> credentials, submit to login rest api, get a token, and then make all >>> other calls passi

Re: AW: Suppress or replace WWW-Authorization header

2015-10-29 Thread tomcat
On 29.10.2015 10:12, chris derham wrote: Torsten, Add an interceptor to AngularJS to detect the 401 and do whatever you want, e.g. redirect to a login page. Then when you have the credentials, submit to login rest api, get a token, and then make all other calls passing this token. There are loa

Re: AW: Suppress or replace WWW-Authorization header

2015-10-29 Thread chris derham
>> Torsten, >> >> Add an interceptor to AngularJS to detect the 401 and do whatever you >> want, e.g. redirect to a login page. Then when you have the >> credentials, submit to login rest api, get a token, and then make all >> other calls passing this token. >> >> There are loads of examples on how

Re: AW: Suppress or replace WWW-Authorization header

2015-10-28 Thread Christopher Schultz
Chris, On 10/28/15 11:55 AM, chris derham wrote: >> No, container BASIC authentication should be enabled, the container should >> handle the authentication, but the browser should not show his ugly default >> login dialog when I request resources from the REST-service with wrong >> credentials. >>

Re: AW: Suppress or replace WWW-Authorization header

2015-10-28 Thread tomcat
On 28.10.2015 16:55, chris derham wrote: No, container BASIC authentication should be enabled, the container should handle the authentication, but the browser should not show his ugly default login dialog when I request resources from the REST-service with wrong credentials. When the REST-client

Re: AW: Suppress or replace WWW-Authorization header

2015-10-28 Thread chris derham
> No, container BASIC authentication should be enabled, the container should > handle the authentication, but the browser should not show his ugly default > login dialog when I request resources from the REST-service with wrong > credentials. > When the REST-client (web-application in the browser)

Re: AW: Suppress or replace WWW-Authorization header

2015-10-28 Thread Aurélien Terrestris
chultz [mailto:ch...@christopherschultz.net] > Gesendet: Mittwoch, 28. Oktober 2015 15:39 > An: Tomcat Users List > Betreff: Re: AW: Suppress or replace WWW-Authorization header > > Torsten, > > On 10/28/15 8:19 AM, Torsten Rieger wrote: > > I have a legacy java-SOA

Re: AW: Suppress or replace WWW-Authorization header

2015-10-28 Thread tomcat
On 28.10.2015 15:39, Christopher Schultz wrote: Torsten, On 10/28/15 8:19 AM, Torsten Rieger wrote: I have a legacy java-SOAP-client that only supports BASIC authentication (send the Authorization: Basic... header) and a AngularJS application that consumes a REST-service (also sending the Autho

Re: AW: Suppress or replace WWW-Authorization header

2015-10-28 Thread Christopher Schultz
Torsten, On 10/28/15 8:19 AM, Torsten Rieger wrote: > I have a legacy java-SOAP-client that only supports BASIC authentication > (send the Authorization: Basic... header) and a AngularJS application that > consumes a REST-service (also sending the Authorization: Basic header). > > The server supp

Re: AW: Suppress or replace WWW-Authorization header

2015-10-28 Thread tomcat
Hi. on this list, as per http://tomcat.apache.org/lists.html#tomcat-users #6 , it is preferred if you respond below the question being asked (or the previous response) rather than on top. (The main reason being that it is easier that way to follow the normal gist of the conversation, rather th