-
Notifications
You must be signed in to change notification settings - Fork 15
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
ringring init #16
ringring init #16
Conversation
const headers = {}; | ||
|
||
const inputMapping = { | ||
'apiKey': input['apiKey'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that the apikey
is present in this file. Could you please move it to the auth.js
file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see https://github.com/clientIO/appmixer-components/issues/1661#issuecomment-1914767748 where I mentioned this. The problem is that OpenAPI spec doesn't support apiKey
in body
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before releasing the generator, we need to improve it or change the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on today's discussion we don't need to do any changes to the generator. When specified like this with apiKey
in body
we simply won't use Authentication section for the component.
Issue: https://github.com/clientIO/appmixer-components/issues/1661
Done
timeScheduled
andtimeValidity
Notes
auth.js
file. TheapiKey
needs to be a part of the body of the POST request to/sms/v1/message
. Due to this, there is no authentication section for the component. Appmixer is not keeping track of any connected accounts.