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

Feature Request: Authenticate with application name/key #63

Open
true2thepen opened this issue Nov 27, 2022 · 0 comments
Open

Feature Request: Authenticate with application name/key #63

true2thepen opened this issue Nov 27, 2022 · 0 comments
Labels
feature-request New feature or request

Comments

@true2thepen
Copy link
Contributor

Ability to authenticate with an application name/key pair instead of user credentials. This would enable all routes to still be protected while giving the ability for an application to have access as at a given role level. This would allow an app to get posts without having to have a user login with their credentials. This would enable the administrator to give access to the site's api without having to have each individual user go through the WordPress application password setup. Ideally, this would give 'guest' privileges to the app until a user signed in through the app. It would require the admin to set up a 'guest' role or set the role to one already available.

Also, an expiry date would auto expire an applications name/key pair. For instance, allow a third party app 30 day access to develop a new front end application for your site. Using the current Simple JWT Login admin page, a separate section for application access could be added where the site administrator could set up the applications name, key and expiry date along with the ability to enable/disable the application's access.

@true2thepen true2thepen added the feature-request New feature or request label Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant