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

Adding CLI and PS error logs & optional audience parameter #159

Merged
merged 8 commits into from Nov 15, 2021

Conversation

BALAGA-GAYATRI
Copy link
Contributor

@BALAGA-GAYATRI BALAGA-GAYATRI commented Oct 25, 2021

Added federated token logs - sample output:
Screenshot 2021-10-25 at 7 00 15 PM

Also, added audience parameter (which will be optional) and defaults to ‘api://AzureADTokenExchange’

@BALAGA-GAYATRI BALAGA-GAYATRI changed the title cherry pick changes Adding federated token logs Oct 25, 2021
@BALAGA-GAYATRI BALAGA-GAYATRI temporarily deployed to Automation test October 25, 2021 13:28 Inactive
@BALAGA-GAYATRI BALAGA-GAYATRI temporarily deployed to Automation test November 1, 2021 11:51 Inactive
@kanika1894 kanika1894 changed the title Adding federated token logs Adding federated token logs & optional audience parameter Nov 1, 2021
@@ -121,7 +121,7 @@ jobs:
az group list
pwd
```
This action supports login az powershell as well for both windows and linux runners by setting an input parameter `enable-AzPSSession: true`. Below is the sample workflow for the same using the windows runner. Please note that powershell login is not supported in Macos runners.
Users can also specify `audience` field for access-token in the input parameters of the action. If not specified, it is defaulted to `api://AzureADTokenExchange`. This action supports login az powershell as well for both windows and linux runners by setting an input parameter `enable-AzPSSession: true`. Below is the sample workflow for the same using the windows runner. Please note that powershell login is not supported in Macos runners.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we should have "This action supports login... " in a new line

@kaverma
Copy link
Contributor

kaverma commented Nov 8, 2021

We need to update the documentation/readme to include the audience field

Copy link
Contributor

@kaverma kaverma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BALAGA-GAYATRI, @N-Usha , should we have a security review to ensure whether we are good with all these claims in logs that anyone can see?

@BALAGA-GAYATRI BALAGA-GAYATRI temporarily deployed to Automation test November 15, 2021 07:05 Inactive
@BALAGA-GAYATRI BALAGA-GAYATRI merged commit 4799d94 into master Nov 15, 2021
BALAGA-GAYATRI added a commit that referenced this pull request Nov 15, 2021
* cherry pick changes

* added audience field option in input params

* added js

* removed extra spaces

* Adding logs to surface AZ-CLI and powershell errors (#171)

* removing token logs
@BALAGA-GAYATRI BALAGA-GAYATRI changed the title Adding federated token logs & optional audience parameter Adding CLI and PS error logs & optional audience parameter Nov 15, 2021
@BALAGA-GAYATRI
Copy link
Contributor Author

Printing token logs changes are removed from this PR and will be done post security approval.

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

Successfully merging this pull request may close these issues.

None yet

2 participants