Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do we specify secrutiyschemes or credentials for callback url ? #1341

Closed
Malligarjunan opened this issue Sep 5, 2017 · 4 comments
Closed

Comments

@Malligarjunan
Copy link

How do we specify secrutiyschemes or credentials for callback url ?
Now that we could pass server b callback url in request. But how do we document or pass the callback url security schemes or defined for that security schemes? some way to specify security credentials like api key during runtime? or do we expect callback urls to be non-protected?

@darrelmiller
Copy link
Member

Callback objects contain Path Item objects. Path Item objects have Operation objects and those Operation objects can have Security objects in the same way regular operations do.

@Malligarjunan
Copy link
Author

Thank you. one more followup question, i can pass the callbackurl as query or header variable values during runtime. how do i pass the credentials?

@darrelmiller
Copy link
Member

During the registration of a callback you can place the callback URL anywhere in the request message. If you also want to pass other information that will be used by the callback, that would need to be an implementation detail. There is currently no way to describe that.

Interestingly, what you are describing is a cross between a link and a callback.

@Malligarjunan
Copy link
Author

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants