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
{{ message }}
This repository has been archived by the owner on Feb 10, 2021. It is now read-only.
On my local environment the application works smoothly however when moving to production i am getting: "The state parameter may have been tampered with!." I think this could be because in my prod environment i have multiple machines.
Because of that i started to check if play-authenticate works as stateless app and found the following pull request: #153
The play-authenticate can be use in a stateless application? and if yes is there an example what i need to change?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On my local environment the application works smoothly however when moving to production i am getting: "The state parameter may have been tampered with!." I think this could be because in my prod environment i have multiple machines.
Because of that i started to check if play-authenticate works as stateless app and found the following pull request: #153
The play-authenticate can be use in a stateless application? and if yes is there an example what i need to change?
The text was updated successfully, but these errors were encountered: