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] WAM Authentication Library Should Support .NET 4.5 for Back Compatibility #3539

Closed
lacomc opened this issue Jul 28, 2022 · 1 comment
Assignees
Milestone

Comments

@lacomc
Copy link

lacomc commented Jul 28, 2022

Is your feature request related to a problem? Please describe.
Previous versions of the library supported older versions of .NET Framework, but newer ones that target NET Standard 2.0 do not. On the other hand, previous versions are not compatible with programs running as elevated processes (see this issue). While the newer library has fixed this issue, there is a gap where there is no way for those stuck on older versions of .NET Framework to successfully use WAM in apps that need to run as elevated processes.

Describe the solution you'd like
A version of the WAM library that supports running as an elevated process from a .NET Framework 4.5 application.

Describe alternatives you've considered

  • Upgrading our application to a newer version of .NET - We've discussed this, but leadership is very hesitant to break back compatibility, meaning this is not a viable short-term option for us.
  • Creating separate executables, one which targets .NET 4.5 (required for back compat) and one that targets a newer .NET version that is compatible with the newer WAM libraries. This is cumbersome and hacky, so not an ideal solution.
  • Cloning the WAM library and re-targeting it ourselves to allow us to use it in our NET 4.5 app. This would likely create more work for both us and the windows auth library team because we would need to maintain code that we don't fully understand and would likely end up needing support from the auth library team.

Additional context
We started the conversation around this already with @bgavrilMS and @gladjohn, who said they believe this is doable.

@gladjohn
Copy link
Contributor

Hi @lacomc please test the private drop @bgavrilMS provided and let us know if that works for you.

@bgavrilMS bgavrilMS linked a pull request Jul 29, 2022 that will close this issue
@pmaytak pmaytak moved this from Triage to In Progress in MSAL Customer Trust / QM Aug 3, 2022
@gladjohn gladjohn moved this from In Progress to Fixed in MSAL Customer Trust / QM Aug 15, 2022
@gladjohn gladjohn modified the milestones: 4.47.0, 4.46.2 Aug 26, 2022
gladjohn added a commit that referenced this issue Aug 26, 2022
Updated Changelog for MSAL 4.46.2

[Feature Request] WAM Authentication Library Should Support .NET 4.5 for Back Compatibility [See 3539](#3539)
Log exceptions which are not converted to MsalExceptions to telemetry. [See #3547](#3547)

[Bug]Authenticator Factory has already been started. [See #3604](#3604)
[Bug] MSAL.NativeInterop only targets .net fwk [See #3612](#3612)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants