Trying to see if OAM gurus would be able to help me out here. I have my App setup for SSO using OAM 14c and OKTA as idp.
Everything was business as usual until one day I got one user reporting an issue with logging in.
Went to oam-diagnostic.log and found error (Session supports encoded objects of upto 20K characters).
It obviously sounds like that user's token is larger than 20k limit? Even though all we use is uid (email address).
Was wondering if anyone ran into situation like that and what was the fix?
Tried to contact AD team but no luck, thinking that maybe modifying LDAP search to more specific group would probably fix that issue.
Any other ideas as to where I can possibly increase that 20k limit or tweak some other properties to fix this annoying and isolated to ONE user issue?
Cheers, John