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
If I want to generate a API token, is there any way to generate by command line or api?
Because I want to write a script that automates the settings of pfsense from scratch and can use the API Token to operate pfsense, but I am stop at unable to generate a TOKEN to use.
Also, sorry for my bad English~.
The text was updated successfully, but these errors were encountered:
Currently, the only way to generate API tokens is within the UI. This is mostly due to concerns over brute force attacks on API tokens, but coincidentally I am working on implementing pfSense's 'Login Protection' feature within the API authentication which will be available in v1.5.0. I can include the ability to generate API tokens from the API itself alongside that feature.
I'll update this issue once a pull request contains the feature.
* feat: generate api tokens via api
allows clients to generate new api tokens from the
/api/v1/access_token endpoint
* docs: updated auth docs
updates readme and openapi docs to state api tokens can
now be updated via api endpoint. also adds section
outlining the purpose of login protection and
how to disable it if needed
* chore: adjust login protection verbage in ui
clarifies that disabling API login protection will not
disble api protection system-wide, only within the api
* tests: added api token auth tests
* tests: fixed order of imports in token tests
* docs: fixed formatting in openapi.yml
the login protection section was missing a trailing newline that bolded the
entire section
Hi,
If I want to generate a API token, is there any way to generate by command line or api?
Because I want to write a script that automates the settings of pfsense from scratch and can use the API Token to operate pfsense, but I am stop at unable to generate a TOKEN to use.
Also, sorry for my bad English~.
The text was updated successfully, but these errors were encountered: