Currently, I have implemented the jwt access and refresh token pattern for client-server communication. The method involves sending two jwt tokens in the header: the access token and the refresh token. This is done by adding the following code to the header:
'Authorization': 'Bearer ' + user.accessToken + ' ' + user.refreshToken
On the server side, I split the request authorization header in order to separate the access token and refresh token. Although this method works for me, I am concerned about its security implications. As a beginner in fetching/auth practices, I want to ensure that I am following recommended security standards. While I understand that my approach may deviate from the norm of using 'Bearer', it has been effective so far. Since I am not integrating with OAuth2 and implementing authentication independently, I would like to continue using this solution if there are no significant security risks associated with it.