Closed LVenn99 closed 2 months ago
Hi LVenn99, Thanks for your questions! We are still developing this standard, and hope to incorporate into it all the reasonable requests from involved parties. Can you please let us know what are your specific ideas regarding OAuth2 and API parameters?
If it's easier for you feel free to reach out to me and we can set up a call to discuss. Kind regards / Met vriendelijke groet,
Steven Reiz Business Analyst Integration Development AZL steven.reiz@azl.eu
Beste @LVenn99, zou je naar opmerking van @sreiz-azl kunnen kijken? Dan hebben wij een beter beeld van de achtergrond van de vraag inzake de OAS specificatie.
Morning, we met with sreiz-azl last week and verified we do have flexibility adding headers and using our own provider for oauth. I have some other suggestions that came up in that call that i will add to github soon.
Indeed :-) (To clarify: REST headers and OAuth provider are not covered in the OpenAPI spec yet, might be hard to standardize in any case).
@dma61 @LVenn99 Luke, I'm assuming this can be closed. Feel free to re-open or create a new issue if you have additional questions.
From the last discussions i derived this can be closed. If not, please reopen.
1) Wat voor flexibiliteit is er voor indivuele partijen om de implementatie van OAuth2 aan te passen om hun APIs te bouwen naar de bedrijfs specificaties? How much flexibility is there for individual parties to modify the implementation of OAuth2 as they see fit to implement their APIs to the company's specifications?
2) Wat voor flexibiltiet is er voor de individuele partijen om de parameters aan te passen om hun APIs te bouwen naar de bedrijfs specificaties? How much flexibility is there for individual parties to add and modify parameters as they see fit to implement their APIs to the firm's specifications