User Community Feedback

Leonardo Straniero

Apr 2, 2021, 9:51 EDT

Good morning staff,
we are developing a web/mobile application (android,iOS) that integrate webex sdk v2.7.0 to start and receive a webex call.

With the aim of starting a new call, we would skip the normal OAuth2 login step with the subsequent opening of a WebView with the insertion of username and password for authentication. This is because we already have the accessToken recovered via the backend thanks to a previous interaction.

We are able to perform this step via SDK Browser writing the following JS code:

if (!webex) {
// eslint-disable-next-line no-multi-assign
webex = window.webex = Webex.init({
config: {
meetings: {
deviceType: 'WEB'
}
// Any other sdk config we need
},
credentials: {
access_token: myAccessToken
}

The problem arises in trying to do the same thing on the mobile app using the iOS SDK (and maybe the SDK Android is the same) because the SDK provides the OAuthAuthenticator class as authentication step to create the webex object as written in your docs/example app, as the following code (that internally and in a protect way invoke the webview):

let authenticator = OAuthAuthenticator(clientId: clientId, clientSecret: clientSecret, scope: scope, redirectUri: redirectUri)
let webex = Webex(authenticator: authenticator)

We think an alternative way to bypass the authentication step and programmatically create the authenticator using our myAccessToken directly as we did successfully from the browser side would be useful.

Best regards,
Leonardo