View in #help on Slack
@Tobie_Desgreniers: Hi all.
Is anyone aware of the problem that arise with the callback URL and OHIF just shows a dark empty window?
Did anyone find a solution to that problem?
@Bill_Wallace: What is the problem?
@Jay_Liu: Are you talking about callback for OIDC?
Problem is usually hidden in browser developer console
@Tobie_Desgreniers: Hi yes I’m talking about the callback for OIDC.
So when I remove all data (cache) from my browser about this site, and I connect “for the first time” I get a dark empty window.
I can get back to you guys with the exact error but it’s something about not finding the object in the storage (cache).
But since it’s the first connection, it shouldn’t search for anything in the cache.
I’ll get back to you in a few hours with the exact error.
The error I get in the developer console is
“Error: Error: No matching state found in storage”
This only happens on the first connection (with empty cache)
@Bill_Wallace: I believe that there is a state value generated when going into OHIF initially, and that state is passed to the remote OIDC connection, and then validated when it comes back. If the state isn’t found, it fails to login. Somehow the state isn’t getting stored correctly - maybe you are starting right with a token?
@Tobie_Desgreniers: Well in my case the login is successful.
But the error “No matching state found in storage” causes the app screen to be completely empty. Nothing is shown.
When I remove everything after the root url to access the app, the app gets loaded correctly.
E.g.
app.com/callback?stage=<hash>&session_state=<hash>…
change it to the following after authentication and state error
app.com
Then the app loads correctly.
@Alireza_Sedghi: What are you using implicit flow? or authorization code flow?
@Tobie_Desgreniers: I’m using the authorization code flow
No one else ever encountered this problem?
@Alireza_Sedghi: Are you using the latest stuff I pushed for Authorization Code Flow?
it was like 1-2 weeks ago
The No matching state found I have seen it when developing it, and it was do to cookies caching
@Tobie_Desgreniers: Yeah I looked at the PR this morning.
I haven’t integrated it yet into my work.
How much time would you say it would take to integrate this latest work on the oauth2 proxy?
@Alireza_Sedghi: It would be 1 hour max
it is worthwhile since the Authorization Code Flow is using another better client library, so i wonder if that has the fix
This one https://github.com/authts/oidc-client-ts
@Tobie_Desgreniers: Cool thank you very much for this estimate.
I’ll integrate the changes and update this thread
@Alireza_Sedghi: cool