Feature request: Add parameter for `client-secret`
See original GitHub issuePlease add a parameter/input for client-secret
removing the need for creds
which is suggestion use of json data structure, which is not recommended by the GitHub team.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5
Top Results From Across the Web
Pass Parameters to Identity Providers - Auth0
Describes how to pass parameters to an Identity Provider API. ... and automatically request access to a specified blog for users when they...
Read more >Ability to Pass Authentication Parameters Individually ... - GitHub
Feature Request : Ability to Pass Authentication Parameters Individually #39 ... and Client Secret as individual parameters instead of bundled in a single ......
Read more >Client ID Enforcement Question - MuleSoft Help Center
Hi,. First time poster here. I'm having some trouble trying to understand the concept around Client ID Enforcement. From all documentation I've read; ......
Read more >Replace an expiring client secret in a SharePoint Add-in
Generate a new secret ... Create a client ID variable with the following line, using the client ID of the SharePoint Add-in as...
Read more >Set up the request — Behat API Extension 3.0.0 documentation
Given I get an OAuth token using password grant from :path with :username and :password in scope :scope using client ID :clientId (and...
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
Thanks for the update. I had two issues:
secrets.AZURE_CLIENT_ID
and notsecrets.azure_client_id
What’s interesting with your answer @lomholdt is that you removed all
***url
(managementEndpointUrl
etc.) and that could be a further optimization for me 😉Closing this issue as we had the workarounds for the same. Please refer readme for more details.