Cheers nmrao
I've found out - they're using OAuth v2.0 with Authorization Code as the grant type - but the solution is a total bodge on that pattern.
The developer has managed to set it up in postman and just to get the authorization token takes 16 sequential REST requests!
I'm just gonna grab the postman collection! :)
nice one!
richie
Hey nmrao
I marked up your response as the accepted solution because this is the only way to close the ticket. and because you did try and help me.
Essentially the whole OAuth v2.0 authentication process is a total bodge and only partially relates to the Authorization Code grant type - ReadyAPI! supports the functionality to support this grant type - but the whole process has been customised to the point it bears no resemblance and isn't transferrable - hence the reason why I didn't add the solution of what I'm doing
The process I'm using has 16 REST requests (a couple POSTs but mostly GETs) and nowhere else would use this approach. Essentially the Technical Architect that was supposed to be reviewing the solution left and the developers did whatever they could to get the process to work - but architecturally - the approach is an antipattern and would never, ever be used elsewhere.
If perhaps one of the forum admins would be able to delete the post - that would make more sense - Olga_T - is there any chance you could delete this topic? ta
Cheers,
richie
Hi richie,
I understand that the situation you faced is very specific, and there is a possibility that nobody else will face it.
However, I would prefer to leave the topic as it is - this may give other users some thoughts or directions where to move forward.
This is what we have a community for. Sometimes, we cannot give the only one solution. However, we can give clues and suggestions for other community members. Does it make sense?
