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

[FEATURE REQ][CAE]Pre-populate user name for InteractiveBrowserCredential #16983

Closed
erich-wang opened this issue Nov 16, 2020 · 4 comments · Fixed by #21082
Closed

[FEATURE REQ][CAE]Pre-populate user name for InteractiveBrowserCredential #16983

erich-wang opened this issue Nov 16, 2020 · 4 comments · Fixed by #21082
Assignees
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved.
Milestone

Comments

@erich-wang
Copy link
Member

erich-wang commented Nov 16, 2020

Library or service name.
What library or service is this request related to?
Azure.Identity

Is your feature request related to a problem? Please describe.
[FEATURE REQ][CAE]Pre-populate user name for InteractiveBrowserCredential

One S500 customer is asking pre-populate user name from Azure PowerShell side, this needs Azure.Identity to support it first.
It is also required for supporting CAE re-authenticate

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 16, 2020
@jsquire jsquire added Azure.Identity Client This issue points to a problem in the data-plane of the library. needs-team-triage Workflow: This issue needs the team to triage. labels Nov 16, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 16, 2020
@erich-wang erich-wang changed the title [FEATURE REQ]Pre-populate user name for InteractiveBrowserCredential [FEATURE REQ][CAE]Pre-populate user name for InteractiveBrowserCredential Apr 6, 2021
@christothes
Copy link
Member

Hi @erich-wang Could you provide a bit more context for why pre-populating the user name is needed? Is this just to save a step of having to re-type it, or is there some other issue that this is meant to address?

@christothes christothes added the needs-author-feedback Workflow: More information is needed from author to address the issue. label Apr 6, 2021
@ghost ghost removed the needs-team-triage Workflow: This issue needs the team to triage. label Apr 6, 2021
@ghost ghost added the no-recent-activity There has been no recent activity on this issue. label Apr 13, 2021
@ghost
Copy link

ghost commented Apr 13, 2021

Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

@NickEales
Copy link

@christothes - Yes - this is so that the customer doesn't have to retype their username.

The (S500) customer had been using this command:

Connect-AzAccount -Tenant XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -Credential $(Get-Credential -Message "Connect-AzAccount" -user $myUser)

The customer has had to enable Conditional Access policies for these users on their domain. The above command uses a User name plus password authentication (ROPC) method that doesn’t support any type of conditional access policy.

@ghost ghost removed the no-recent-activity There has been no recent activity on this issue. label Apr 14, 2021
@ghost ghost added the no-recent-activity There has been no recent activity on this issue. label Apr 21, 2021
@ghost
Copy link

ghost commented Apr 21, 2021

Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants