Skip to content

Ensure HTTP behavior is consistent with other MSALs #961

Open
@Avery-Dunn

Description

@Avery-Dunn

Currently, HTTP-related classes in MSAL Java are difficult to maintain and test:

  • A few core classes contain most of the behavior, but there are more than a dozen classes containing some aspect of our HTTP calls
  • The original implementation and ad hoc changes over the years do not follow Java best practices for interfaces, builders, factories, etc.
  • The overall structure and internal APIs have little in common other MSALs

These classes should be investigated to identify how they can follow modern Java design principles, and to ensure that their structure and behavior is consistent with other MSALs, particularly MSAL .NET

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal priority items, should be done after P1SDK-ConsistencyItems that deal with consistency between all MSALsconfidential-clientFor issues related to confidential client appspublic-clientFor questions/issues related to public client apps

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions