1. Sabir Foux
  2. PowerServer Web
  3. Sunday, 8 September 2019 16:44 PM

I have a log in window that connects to Okta, retrieves the user profile and from there the connection string, and then uses that connection string to connect to the proper database. User A is able to log in just fine.

I created a new user and assigned him the same connection string that I copied from User A, however when I try to log in as this new user it says "Connection cache name cannot be null." 

I displayed the MessageBox to output the cache name just in case it was missing from the json returned from Okta. However I can see that it is properly returning the cache name in the connection string. 

What would cause it to miss the value even though it works for one user and not the other?

Thank you

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Sunday, 8 September 2019 16:53 PM
  2. PowerServer Web
  3. # Permalink
0
Votes
Undo

Hi Sabir;

  If the Cache name has a space  in it ...could that space actually be a "null" or a non-displayable character of some kind?

Regards ... Chris

Comment
I can close this ticket now. The problem was formatting issue with the response from Okta containing the connection string. When PB received that json it was looking for the connection string in the wrong place. By correcting the format in Okta for that user PB could read the connection string.



TLDR: The problem was with Okta, not powerbuilder/server.
  1. Sabir Foux
  2. Monday, 9 September 2019 01:04 AM
Hi Sabir;

Glad that you found your issue!

Regards ... Chris
  1. Chris Pollach @Appeon
  2. Monday, 9 September 2019 02:15 AM
There are no comments made yet.


There are replies in this question but you are not allowed to view the replies from this question.