MongoAtlas-> Stitch: Generating token using utils.jwt.encode
Frontend-StitchBrower: Use of CustomProvider using the returned token to connect the user
Frontend-StitchBrower: Connection made successfully
Problem: When I send the for Authentication TypejwtTokenString header I get the following error "signingKeys must not be blank"
Can you explain to me why after using CustomProvider the token generated by Stitich in the access_token property IS NOT EQUAL TOKEN SENT as a parameter to the CustomProvider, I don't understand?
Hello,
I am doing the following
Problem: When I send the for Authentication Type jwtTokenString header I get the following error "signingKeys must not be blank"
Can you explain to me why after using CustomProvider the token generated by Stitich in the access_token property IS NOT EQUAL TOKEN SENT as a parameter to the CustomProvider, I don't understand?