-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Split classes out into files #2
Conversation
@shivbijlani, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
static get accessToken(): string { return "access_token"; } | ||
static get expiresIn(): string { return "expires_in"; } | ||
static get sessionState(): string { return "session_state"; } | ||
static get tokenKeys(): string { return "adal.token.keys"; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as a part of refactor can we replace all "adal" with "msal"?
@@ -1,14 +1,18 @@ | |||
{ | |||
"compileOnSave": true, | |||
"compilerOptions": { | |||
"target": "es5", | |||
"module": "commonjs", | |||
"target": "es5", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rohitnarula7176 - I thought we were targeting es6?
[msal-node][#2] Merge cache logic in `msal-common` for `node` and `browser` platforms
[msal-extensions] Extensions #2
Telemetry #2: Implement Telemetry in msal-browser
Broker #2: Sending auth requests
AT Proof-Of-Possession #2: Handle proof-of-possession tokens correctly in responses
* Add KeyManager class * Add STK JWK to BaseAuthRequest * Add STK generation logic to common and browser * Update PublicClientApplication tests to mock out STK generation from Auth Code requests * Undo msal-node-samples changes * Move generateCnf from PopTokenGenerator to KeyManager * Refactor crypto key generation to use different key generation algorithm options for AT and RT PoP * Add missing API from Crypto Interface to msal-node * Fix linter issues * Add rtPop msal-browser sample * Add stk_jwk to /authorize call in AuthorizationCodeClient to initiate bound rt flow * Add STK JWK to /token request to obtain bound rt response * Add stkJwk to AuthorizationCodeClient tests * Update mock crypto interface in tests * Fix merge conflicts * Cleanup tests * Refactor Cryptographic constants out of BrowserConstants and CryptoOps * Fix generatePublicKeyThumbprint stubs and expected values on tests * Fix tests after merge * Add feature flag to make RT Binding opt-in * Add error handling to STK generation step * Refactor crypto enum names * Add error handling for crypto key generation * Put KeyManager instance in BaseClient instead of AuthCode and Refresh Clients * Fix import in BaseClient * Extend KeyManager tests * Increase test coverage * Update lib/msal-browser/src/utils/CryptoConstants.ts * Fix merge conflicts * Add boundRT sample * Undo unnecessary method position change * Add initial e2e tests for RT PoP * Revert to headless false for boundRT e2e test * Update lib/msal-common/test/client/RefreshTokenClient.spec.ts Co-authored-by: Thomas Norling <thomas.l.norling@gmail.com> * Fix incorrect typing and checks for private key on getPublicKeyThumbprint * Refactor cryptographic constants to have more consistent casing * Fix CryptoOps tests around getPublicKeyThumbprint * Move refreshTokenBinding feature flag to system config * Update browser client config to move refreshTokenBinding flag to system config * Rename KeyManager to CryptoKeyManager for more specificity * Update BrowserAuthError to remove keyId from error message and avoid Pii * Update lib/msal-browser/src/config/Configuration.ts * Update sample and fix merge bugs * Remove CryptoKeyManager class Co-authored-by: Thomas Norling <thomas.l.norling@gmail.com>
Msal-common post release January 2023 patch #2
Splits up /authorize request generation into separate functions for 1. Standard params (included on all requests) 2. Browser auth code params 3. Node auth code params Note: #7633 adds another for Browser EAR Note2: Future (uncommitted) work to move /token and /logout to a similar pattern for extensibility and bundle size improvements
No description provided.