AW: AW: Suppress or replace WWW-Authorization header

: Donnerstag, 29. Oktober 2015 15:02 An: Tomcat Users List <users@tomcat.apache.org> Betreff: Re: AW: Suppress or replace WWW-Authorization header Chris, On 10/29/15 5:12 AM, chris derham wrote: >>> Torsten, >>> >>> Add an interceptor to AngularJS to detect the 401 and do wha

AW: AW: AW: Suppress or replace WWW-Authorization header

I want to say thank you all for your help and many different ways to solve my problem. I think the most -maybe all- will work in an ideal world without hard requirements through legacy client-applications. I don't want to hold on BASIC as auth-method because I like it so much, I prefer to kick

Re: AW: AW: Suppress or replace WWW-Authorization header

> I want to say thank you all for your help and many different ways to solve > my problem. I think the most -maybe all- will work in an ideal world without > hard requirements through legacy client-applications. I don't want to hold > on BASIC as auth-method because I like it so much, I prefer to

Re: AW: AW: Suppress or replace WWW-Authorization header

Am 31.10.2015 1:39 vorm. schrieb chris derham : > > > I want to say thank you all for your help and many different ways to solve > > my problem. I think the most -maybe all- will work in an ideal world > > without > > hard requirements through legacy client-applications. I

AW: AW: AW: Suppress or replace WWW-Authorization header

-Ursprüngliche Nachricht- Von: André Warnier (tomcat) [mailto:a...@ice-sa.com] Gesendet: Mittwoch, 28. Oktober 2015 20:42 An: users@tomcat.apache.org Betreff: Re: AW: AW: Suppress or replace WWW-Authorization header On 28.10.2015 17:42, Torsten Rieger wrote: > -Ursprüngliche Nachri

Re: AW: Suppress or replace WWW-Authorization header

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

Re: AW: Suppress or replace WWW-Authorization header

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

Re: AW: Suppress or replace WWW-Authorization header

>> 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

AW: Suppress or replace WWW-Authorization header

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 supports two kinds of deployment: Standalone with an embedded

Re: AW: Suppress or replace WWW-Authorization header

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

Re: AW: Suppress or replace WWW-Authorization header

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

Re: AW: Suppress or replace WWW-Authorization header

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

AW: AW: Suppress or replace WWW-Authorization header

-Ursprüngliche Nachricht- Von: Christopher Schultz [mailto:ch...@christopherschultz.net] Gesendet: Mittwoch, 28. Oktober 2015 15:39 An: Tomcat Users List <users@tomcat.apache.org> Betreff: Re: AW: Suppress or replace WWW-Authorization header Torsten, On 10/28/15 8:19 AM, Torsten

Re: AW: Suppress or replace WWW-Authorization header

--- > Von: Christopher Schultz [mailto:ch...@christopherschultz.net] > Gesendet: Mittwoch, 28. Oktober 2015 15:39 > An: Tomcat Users List <users@tomcat.apache.org> > Betreff: Re: AW: Suppress or replace WWW-Authorization header > > Torsten, > > On 10/28/15 8:19 AM, Torsten

Re: AW: Suppress or replace WWW-Authorization header

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

> 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)

AW: AW: Suppress or replace WWW-Authorization header

-Ursprüngliche Nachricht- Von: Aurélien Terrestris [mailto:aterrest...@gmail.com] Gesendet: Mittwoch, 28. Oktober 2015 16:45 An: Tomcat Users List <users@tomcat.apache.org> Betreff: Re: AW: Suppress or replace WWW-Authorization header You can choose between a pop-up or an HTM

RE: AW: AW: Suppress or replace WWW-Authorization header

On 28.10.2015 17:42, Torsten Rieger wrote: > -Ursprüngliche Nachricht- > Von: Aurélien Terrestris [mailto:aterrest...@gmail.com] > Gesendet: Mittwoch, 28. Oktober 2015 16:45 > An: Tomcat Users List <users@tomcat.apache.org> > Betreff: Re: AW: Suppress or replace WWW

Re: AW: AW: Suppress or replace WWW-Authorization header

On 28.10.2015 17:42, Torsten Rieger wrote: -Ursprüngliche Nachricht- Von: Aurélien Terrestris [mailto:aterrest...@gmail.com] Gesendet: Mittwoch, 28. Oktober 2015 16:45 An: Tomcat Users List <users@tomcat.apache.org> Betreff: Re: AW: Suppress or replace WWW-Authorization header Y

Re: AW: AW: Suppress or replace WWW-Authorization header

On 10/28/2015 12:04 PM, André Warnier (tomcat) wrote: The server supports two kinds of deployment: Standalone with an embedded Jetty-server and as war-file for app-servers (most of them are tomcat-server). I try to suppress the browser BASIC-login-dialog for the REST-service-calls from

Re: AW: AW: Suppress or replace WWW-Authorization header

Torsten, On 10/28/15 11:28 AM, Torsten Rieger wrote: > -Ursprüngliche Nachricht- > Von: Christopher Schultz [mailto:ch...@christopherschultz.net] > Gesendet: Mittwoch, 28. Oktober 2015 15:39 > An: Tomcat Users List <users@tomcat.apache.org> > Betreff: Re: AW: Su

Re: AW: AW: Suppress or replace WWW-Authorization header

On 28.10.2015 17:42, Torsten Rieger wrote: -Ursprüngliche Nachricht- Von: Aurélien Terrestris [mailto:aterrest...@gmail.com] Gesendet: Mittwoch, 28. Oktober 2015 16:45 An: Tomcat Users List <users@tomcat.apache.org> Betreff: Re: AW: Suppress or replace WWW-Authorization header Y

Re: AW: Suppress or replace WWW-Authorization header

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.