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 Request] Integration test with refrehs_in #4946

Open
bgavrilMS opened this issue Sep 26, 2024 · 0 comments · May be fixed by #4962
Open

[Feature Request] Integration test with refrehs_in #4946

bgavrilMS opened this issue Sep 26, 2024 · 0 comments · May be fixed by #4962

Comments

@bgavrilMS
Copy link
Member

MSAL client type

Confidential

Problem statement

We don't have any integration test around refresh_in. This is just to observe that ESTS issues it, to avoid regressions such as MSAL changes sku and ESTS stops sending it. Functioanal aspect of refresh_in is covered by other tests.

Proposed solution

No response

Alternatives

No response

@bgavrilMS bgavrilMS added untriaged Do not delete. Needed for Automation needs attention Delete label after triage Feature Request internal confidential-client QM ic3 and removed untriaged Do not delete. Needed for Automation needs attention Delete label after triage ic3 labels Sep 26, 2024
@bgavrilMS bgavrilMS linked a pull request Oct 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Committed
Development

Successfully merging a pull request may close this issue.

1 participant