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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: