IT4Change/gradido
3
0
Fork 0
mirror of https://github.com/IT4Change/gradido.git synced 2025-12-13 07:45:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

"implemented" logout call

Browse Source
This commit is contained in:
Ulf Gebhardt 2021-11-11 00:14:03 +01:00
parent 6ab381a6b1
commit e896759e1e
Signed by: ulfgebhardt
GPG Key ID: DA6B843E748679C9
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
backend/src/graphql/resolver/UserResolver.ts
View File

@ -263,13 +263,13 @@ export class UserResolver {
@Authorized() @Authorized()
@Query(() => String) @Query(() => String)
async logout(@Ctx() context: any): Promise<string> { async logout(@Ctx() context: any): Promise<boolean> {
const payload = { session_id: context.sessionId } // TODO: We dont need this anymore, but might need this in the future in oder to invalidate a valid JWT-Token.
const result = await apiPost(CONFIG.LOGIN_API_URL + 'logout', payload) // Furthermore this hook can be useful for tracking user behaviour (did he logout or not? Flag him if he didn't on next login)
if (!result.success) { // The functionality is fully client side - the client just needs to delete his token with the current implementation.
throw new Error(result.data) // we could try to force this by sending `token: null` or `token: ''` with this call. But since it bares no real security
} // we should just return true for now.
return 'success' return true
} }
@Mutation(() => String) @Mutation(() => String)