Replies: 1 comment
-
@dpardhi , the Authentication component acts as a central registry for different Authentication strategies. It is up to the API developer to do the following.
Each new strategy has its own unique name within your application (ie: 'jwt', 'mickey', 'pluto'), you the extension developer give to it its unique name. On the class method or class definition level you just place the decorator @authenticate('jwt','pluto')
export class TestingController {
constructor(
@inject(SecurityBindings.USER)
private userProfile: UserProfile, // ------------- END OF SNIPPET -------------
) {} or at the method level @authenticate('jwt','pluto')
@get('/whoami')
whoAmI(): string {
return this.userProfile[securityId];
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Beta Was this translation helpful? Give feedback.
All reactions