Authorization: check application ID
See original GitHub issueThe sandbox token format includes a applicationID
field, but the ledger API does not use it to for validation - it is currently only read by the JSON ledger API.
We should add the application ID to Claims, then use it in the ledger API service auth validation if present.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Get application ID and authentication key
When logging in programmatically, you need the ID for your application and an authentication key. To get those values, use the following steps:....
Read more >Authorization Check - an overview | ScienceDirect Topics
It is based on performing all necessary authorization checks, when a user executes an activity on the SAP J2EE Engine, to ensure that...
Read more >Configure Azure AD authentication - App Service
Sign in to the Azure portal, search for and select App Services, ... Select Expose an API, and click Set next to "Application...
Read more >App ID Authorization V4 | IBM Cloud API Docs
When users or backend services interact with your app, they might need to be authorized to perform specific actions. App ID verifies that...
Read more >Official ESTA Application Website, U.S. Customs and Border ...
Welcome to the Electronic System for Travel Authorization ... You want to apply for a new authorization for one person or a group...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My question was not regarding the missing
applicationId
from a request but the behavior of tokens with anapplicationId
against a service that does not have such a field. As I mentioned before, I will simply ignore it for the time being. If there are different requirements we can address them separately.@stefanobaghino-da IMO the ledger should behave as follows:
i.e.,