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

JWT encoding is not working #1975

Closed
nelkon opened this issue Jul 4, 2023 · 1 comment
Closed

JWT encoding is not working #1975

nelkon opened this issue Jul 4, 2023 · 1 comment

Comments

@nelkon
Copy link

nelkon commented Jul 4, 2023

Description

API invocation fails when enabling the backend JWT.

Steps to Reproduce

  • Get an APIM 4.1 pack and update to level 79 or the latest.
  • Enable backend JWT with the below configurations.

[apim.jwt]
enable = true
header = "X-JWT-Assertion"
enable_user_claims = true
Furthermore add the below set of application attributes as well.

[[apim.devportal.application_attributes]]
required=true
hidden=false
default="Yes"
name="Sandbox access required ?"
description="Does this Application require access to APIs in the Sandbox environment ? (Yes or No)"

[[apim.devportal.application_attributes]]
required = true
hidden = false
name = "date_Review Date"
description = "What date should API access terminate or be reviewed?"

[[apim.devportal.application_attributes]]
required = true
hidden = false
name = "date_Start Date"
description = "test"

[[apim.devportal.application_attributes]]
required=true
hidden=false
default="Yes"
name="Production access required ?"
description="test"

[[apim.devportal.application_attributes]]
required=false
hidden=false
name="Sponsor's name"
description="Person responsible for the project this Application represents"

[[apim.devportal.application_attributes]]
required=false
hidden=false
name="Usage description"
description="What is the purpose/service/project/product of the Application requiring API access ?"

Login to the carbon management console and create a user by providing the username as “admin.abc”
Go to the devportal and create a new application, subscribe API, generate keys and invoke the API.
The first invocation will work, but you’ll observe the same error from the second invocation onwards.
As per these observations, the issue occurs even without a custom JWT generator

Affected Component

APIM

Version

4.1.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants