Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Manjunatha Mn (ManjunathaM6763)
ING Vysya Bank Ltd

ING Vysya Bank Ltd
NL
ManjunathaM6763 Member since 2017 6 posts
ING Vysya Bank Ltd
Posted: Jun 11, 2018
Last activity: Jun 18, 2018
Posted: 11 Jun 2018 18:00 EDT
Last activity: 18 Jun 2018 13:21 EDT
Closed

Authorization header

Hi We are using container managed authentication in tomact by using realm configuration which connects to LDAP and validates the credentials which is working fine. We have a challenge when we login with container managed authentication URL(PRServletContainerAuth) we see authorization header is getting generated which is having username and password with base64 encoded. How to avoid creating this Header or enable different encoding.

***Edited by Moderator Marissa to update platform capability tags***

To see attachments, please log in.
Security

Posted: 6 years ago
Posted: 18 Jun 2018 12:31 EDT
Chris Koyl (ChrisKoyl)
PEGA
Senior Fellow, Technical Support, Runtime Engine
Pegasystems Inc.
US

The adding of the Authentication header really only occurs when BasicAuth is used. This is going to be your tomcat configuration. Do you mind posting some of the realm configuration or at least the class that is handling the authentication?

 

 

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice