We have created the sub-account and created the application for testing. We have a few questions about the same.
We have chosen OAuth server-to-server authentication but key their token expiration is only for one hour can we extend the token time? If Yes, kindly share the maximum token timeline.
If we move from JWT to OAuth then our old appointment will work the same just the same?
We already start the implementation of OAUth. Will someone help in the migration process on call because we don’t have any idea how to migrate from JWT to OAuth?
Can we have video help that demonstrates how to do the migration from JWT to OAuth from dev login – where we create an application in developer login?
We have chosen OAuth server-to-server authentication but key their token expiration is only for one hour can we extend the token time? If Yes, kindly share the maximum token timeline.
If we move from JWT to OAuth then our old appointment will work the same just the same?
Answer: Any meetings which has already been scheduled will still be valid. These “old appointments” will still be there on your account. For OAuth, the REST endpoints to schedule meeting is still the same.
We already start the implementation of OAUth. Will someone help in the migration process on call because we don’t have any idea how to migrate from JWT to OAuth?
Answer: I would recommend you to raise a ticket for this.
Can we have video help that demonstrates how to do the migration from JWT to OAuth from dev login – where we create an application in developer login?
Answer: Could you elaborate on this?
please tag me in your response to get my attention. thanks