Add and Configure MarketPay payment method (preferrence and BM configuration validate) #9
Conversation
sf-technolgies
changed the title
| log.info("GetService Marketing _url:" + svc.getURL()+'/'+serviceType); | ||
| log.info("GetService token:" + payload.token); | ||
| log.info("GetService Marketing _url:" + svc.getURL() + '/' + serviceType); | ||
| log.info("GetService token:" + getAuthToken()); |
There was a problem hiding this comment.
Is it really a good idea to log the token ? Maybe just a portion of it ?
| svc.setRequestMethod(method); | ||
| svc.addHeader('Content-Type', 'application/json'); | ||
| svc.addHeader('Authorization', 'Bearer ' + payload.token); | ||
| svc.addHeader('Authorization', 'Bearer ' + getAuthToken()); |
There was a problem hiding this comment.
You are calling getAuthToken when logging, and then getAuthToken again when setting the headers, so fundamentally you are creating two tokens for the same request, and logging only one of them.
That sounds wrong.
There was a problem hiding this comment.
@emicha I have removed the getAuthToken that was logged also we are caching the token for 3500 seconds and fetching the token from that and if not found we fetch the fresh token.
There was a problem hiding this comment.
What do you mean caching?
When you work with 1 session, you need to always use the same token.
When you work with a different session, you should have a different token.
Is that implemented?
4 participants
Uh oh!
There was an error while loading. Please reload this page.