How to fix Memberstack API authorization errors when updating user fields from Discord OAuth2?
Hey guys,
I have problems regarding Memberstack API. I have bot code that is on GitHub and deployed on Heroku, that bot gives user "Authorization" Discord page (OAuth2) and when user authorizes he gets added to my Discord server, but when he joins Discord server his discord username should be grabbed and put in Memberstack field "discord" of that user that clicked button - this is done by his memberstack user ID.
In heroku logs its showing that all the process works perfectly until its time to update Memberstack field. I have tried multiple methods and these are the errors that showed up:
I have problems regarding Memberstack API. I have bot code that is on GitHub and deployed on Heroku, that bot gives user "Authorization" Discord page (OAuth2) and when user authorizes he gets added to my Discord server, but when he joins Discord server his discord username should be grabbed and put in Memberstack field "discord" of that user that clicked button - this is done by his memberstack user ID.
In heroku logs its showing that all the process works perfectly until its time to update Memberstack field. I have tried multiple methods and these are the errors that showed up:
1: OAuth2 error: HTTP error! status: 403, body: {"message":"Authorization header requires 'Credential' parameter. Authorization header requires 'Signature' parameter. Authorization header requires 'SignedHeaders' parameter. Authorization header requires existence of either a 'X-Amz-Date' or a 'Date' header. Authorization=*my secret key*"}
2: OAuth2 error: HTTP error! status: 403, body: {"message":"'*my secret key*' not a valid key=value pair (missing equal-sign) in Authorization header: 'Bearer *my secret key*'."}
2: OAuth2 error: HTTP error! status: 403, body: {"message":"'*my secret key*' not a valid key=value pair (missing equal-sign) in Authorization header: 'Bearer *my secret key*'."}
Comments
1 comment
Hey Igor Zeljkovic
Thank you for posting. I think we would need additional info to help solve this issue. Can you create a support ticket for this please?
Please sign in to leave a comment.