You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frontend sends a request to the backend that is handled by the authenticate function specified above.
The backend answers with a redirect to the authorize endpoint, the front end catches it and redirects to the url ( by setting the window.location)
The user logs in and then the a request is sent to the redirect_uri with the authorization code.
And I get the error "Undefined index: openid_connect_state"
However, when I hit the Controller authenticate function directly:
he backend answers with a redirect to the authorize endpoint, the front end catches it and redirects to the url
The user logs in and then the a request is sent to the redirect_uri with the authorization code.
And then requests a token and everything works fine.
The text was updated successfully, but these errors were encountered:
Pull Request #251 would fix this. Because I don’t want to wait until jumbojett reacts, I forked this library and added this functionality. I will add some other improvements in the future.
I have a backend project (Laravel php)
And a frontend project (Vue js)
I created an authenticate function in a controller:
The frontend sends a request to the backend that is handled by the authenticate function specified above.
The backend answers with a redirect to the authorize endpoint, the front end catches it and redirects to the url ( by setting the window.location)
The user logs in and then the a request is sent to the redirect_uri with the authorization code.
And I get the error "Undefined index: openid_connect_state"
However, when I hit the Controller authenticate function directly:
he backend answers with a redirect to the authorize endpoint, the front end catches it and redirects to the url
The user logs in and then the a request is sent to the redirect_uri with the authorization code.
And then requests a token and everything works fine.
The text was updated successfully, but these errors were encountered: