Forum Discussion
Getting a 401 only on select REST calls (token auth)
- Apr 20, 2018
Figured this out a little while ago and it has to do with the loginProviderName in the JSON object sent. When setting
"loginProviderName": "tmos"
against a BIG-IQ, this will fail hard, so I had removed this property from the login request object in a shared function I was using. Eliminating this property will allow token generation from a BIG-IP with read privileges, but will not allow writing.
GET requests to:
/mgmt/shared/authz/tokens
will list you available tokens.Maybe it is a problem related to how the token is parsed ? Capturing the traffic might help.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com