Angular - authentication headers

Question

I have an Java backend that provides me some API's that are protected with authentication.

So if I call it using any browser or postman with Authorization I have an 200 (Ok) response, but If I set httpHeaders with the same user and password, I get 401 (Unauthorized).

The call:

let username: string = 'admin';
let password: string = 'pe';
let headers =  new HttpHeaders().set('Authorization' , 'Basic ' + btoa(username + ':' + password)).set('Content-Type', 'application/json').set('cache-control', 'no-cache'); 
console.log(headers);

let params = new HttpParams().set('instID', value).set('procType', 'M');
    
return this.httpClient.get<pe_process_instance[]>('http://' + this.urlConfig.BASE_URL + ':' + this.urlConfig.PORT + '/' + this.urlConfig.WSBaseURL + '/getipeprocessinstances', { headers: headers , params: params });

The response:

What I am missing here? Do I correctly set my headers?

Well, this seems to fail on the options request, seems to me that this is a CORS issue. Have you correctly setup CORS in backend? — AVJT82
– AVJT82, Commented Jan 25, 2019 at 17:11

kris_IV · Accepted Answer · 2019-01-25 11:16:04Z

1

Try to set your headers in this way:

let headers = new HttpHeaders();

headers = headers.append('Authorization', 'Basic ' + btoa(username + ':' + password));
headers = headers.append('Content-Type', 'application/json');
headers = headers.append('cache-control', 'no-cache');

When you use .set() multiple times you overwrite your headers each time, and only last header is send.

answered Jan 25, 2019 at 11:16

kris_IV

2,4642 gold badges26 silver badges43 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

kris_IV Over a year ago

I think that I have another idea why you have a problem with this request. Look, that 401 you get for Option request, not for GET and this is a difference between your browser version and REST client request, where you don't have CORS issue. I think that your problem is not a Angular App but Java server. In normal way you should get 200 from OPTION and eventually 401 from GET. I think that you should disable OPTION request from your Authentication process.

Kiril1512 Over a year ago

you mean disable OPTION in the back-end?

kris_IV Over a year ago

Not disable OPTION, but disable authentication for OPTION request. I had similar problem few years ago with PHP Symfony framework, and I found solution where OPTION request get round authentication process. This is very important because OPTION request doesn't have custom headers, so authentication can't pass for them.

kris_IV Over a year ago

Did you found solution?

Collectives™ on Stack Overflow

Angular - authentication headers

1 Answer 1

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related