Skip to content

Token endpoint invocation makes different behaviours based on token_persistence config #4936

@RusJaI

Description

@RusJaI

When invoking the token endpoint directly, under default configs, each invocation to token endpoint returns a new access token.
When the following config is set,

[oauth.token_persistence]
enable=true 

it invalidates the previously generated token. Hence only the token generated from the last request to token endpoint is a valid token.

Is this behaviour expected ?

Please find the sample curl :

curl -k -X POST https://localhost:9443/oauth2/token -d "grant_type=password&username=Username&password=Password" -u "<CONSUMER_KEY>:<CONSUMER_SECRET>"

Metadata

Metadata

Assignees

No one assigned

    Labels

    4.7.0Label for General Availability Release of APIM 4.7.04.7.0-BetaAPI Manager 4.7.0 – Beta Release

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions