Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

some feature for wordpress plugin #869

Closed
stephenwongcandr opened this issue Feb 2, 2023 · 1 comment
Closed

some feature for wordpress plugin #869

stephenwongcandr opened this issue Feb 2, 2023 · 1 comment

Comments

@stephenwongcandr
Copy link

  1. is that possible to regenerate the session id after clicking logout?
  2. how can federated logout the account without invalid state? (since I added the federated logout
  3. when I using universal login page, it will pass the parameters in URL to authorize, is that possible to change it as post body instead of URL parameters? or the parameters is fine to read?
@evansims
Copy link
Member

evansims commented Feb 6, 2023

Hi @stephenwongcandr 👋 Thanks for your questions! Presumably you're using v4 of the plugin?

  1. is that possible to regenerate the session id after clicking logout?

The WordPress plugin works off the native WP session, so you can hook into the wp_logout event to perform any extra actions you need. You'd need to refer to the WordPress API to determine if that's possible.

  1. how can federated logout the account without invalid state? (since I added the federated logout

An invalid state occurs when a user lands on the callback route without a valid state and code. The callback route is only used for completing the authentication flow, after the user is returned from the Universal Login Page. Your logout shouldn't be returning the user to the callback route if that is the case.

when I using universal login page, it will pass the parameters in URL to authorize, is that possible to change it as post body instead of URL parameters? or the parameters is fine to read?

This is normal and not changeable. It's part of the design Authorization Code Flow. The WordPress plugin is considered a confidential client, as it stores the secret server side. As such, the parameters are safe to send as parameters of a GET request, as they do not contain any dangerous secrets.

@evansims evansims closed this as completed Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants