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.

Discussion

 Naveen Mandapati (NaveenM4274)
Tech Mahindra
Lead System Architect
Tech Mahindra
CA
NaveenM4274 Member since 2014 17 posts
Tech Mahindra
Posted: Jul 24, 2015
Last activity: Jul 28, 2015
Posted: 24 Jul 2015 10:43 EDT
Last activity: 28 Jul 2015 19:35 EDT
Closed

Not able to set Properties during Authentication - PRCustom Authentication

Hello there,

I am reading some information from cookies in a PRCustom Authentication like Transit ID and Role and setting them in "Operator" page.  I am getting the following error in logs with failed authentication 

 

Authentication failed because the constructed Data-Admin-Operator-ID instance failed to pass validation.  The most likely cause for this is that your Data-Admin-AuthService record attempts to map directory attributes to PROPERTIES THAT DO NOT BELONG TO DATA-ADMIN-OPERATOR-ID class.  Check your D-A-AuthService record for bad entries or typos.

 

This is only happening when i am setting the custom application properties, if i remove them it seems to work fine. 

Are we not supposed to update any data to operator during authentication ?

We are using pega V7.1.7,

 

Thanks

NM

To see attachments, please log in.
Security

Posted: 9 years ago
Posted: 27 Jul 2015 22:34 EDT
Ashok Kumar Bommisetty (Ashok_Bommisetty)
Areteans Technology

Areteans Technology
IN

Naveen,

Good  question. First of all check if the properties are created in the inheritance path of Data-Admin-Operator-ID class. Second check the mapping in your authservice rule. Third, the most trickiest, make sure these properties are available for the access group of PegaRULES:Unauthenticated.

The initial requestor before authentication should have access to your custom properties before setting its own requestor accessgroup and ruleset stack.

 

 

Thanks,

Ashok

To see attachments, please log in.
Posted: 9 years ago
Posted: 28 Jul 2015 10:49 EDT
Naveen Mandapati (NaveenM4274)
Tech Mahindra
Lead System Architect
Tech Mahindra
CA

Thanks Ashok for the response, found the root cause

 

It was silly mistake, the properties that were created are not in the unauthenticated ruleset, that's why the validation was failing. 

 

Thanks

Naveen

To see attachments, please log in.

Related content:

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