Discussion
FTB
US
Last activity: 6 Apr 2018 19:26 EDT
SSO is not working after upgrade to PRPC7 ML7
SSO is not working and found the below log entry:
ERROR|WebContainer : 3|2015-04-24 09:13:20,074|com.pega.pegarules.session.internal.mgmt.authentication.SchemePRCustom|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.|H13A8FEBBFC89357260D59C968B3AFBD5x1|
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
FTB
US
In ML7 the functionality of Tracking changes on a data instance is not working as the function that writes the history record uses a new property called pyPropertyIndex (which is a String instead of an Integer as expected).
The property only exists in Embed-ModelParams class and not @baseclass so for an Operator record (Data-Admin-Operator-ID) it would not find it. The operator record is however initially saved. The operator record cannot subsequently be changed as validation fails when it sees this property on the operator top-level page.
The HFix-20074 addresses this issue.