Page Comparison

...

The same interface can be used for Wrangler_ and test_mate, but each of these require requires different Scope permissions. This example will show setting up Wrangler_ for Webex Scopes.

Press Submit

...

Info
Proxy is optional, ; Internet access is required to access https://webexapis.com/ from Yarnman.

Display Permissions required to be setup set up in Webex integration

When the page saves, Press show press Show Scopes

These are the requires required roles to be configured on your webex Webex integration

...

Create Webex Integration

Open a new Tab/Browser to Create a new Webex integration: https://developer.webex.com/my-apps

...

Note
Service integration with static auth_token are is not supported at this time

Set

...

Webex permissions

Complete the required fields (we will come back to the redirect uriURI), select or upload a logo, and scroll down to select choose the scopes to match the ones shown from Yarnman.

...

Find Redirect URL from yarnman

...

Select the Yarnman node in the dropdown, followed by pressing Bind to Arm

...

Save redirect URL in Webex integration.

Copy the URL that is shown as Redirect URL and switch back to Webex

Paste in the URl URL to the URL field, and make sure to remove any leading Spaces or Tabs that may come through

...

Save Integration and obtain a Client ID and Secret

Press Add in Webex

Make note of the Client ID, Client Secret ( NOTE: this won't be shown again , however it can be regenerated if lost)

...

Start oAuth flow with Set Credentials

Switch back to Yarnman

press Press Update / Set Credentials

Populate

Application with either the same as your you called it in Webex or something meaningful.

Client ID as string provided by Webex

Redirect URI as the one provided supplied by yarnman and press submit

...

The popup will refresh with an Authorise button with the confirmed details, ; Press Authorise to obtain the oAuth OAuth Token

...

Note
The web browser will required require Internet Access and Access to Yarnman, . Please make sure your Jumpbox or Proxy settings in the browser allow for this configuration. If you have a proxy in your browser, you may need to bypass the Yarnman's IP address of Yarnman if you have a proxy in your browser.

The webex Webex authentication screen will be presented. Depending on your environment, this could be handled by Webex or your SSO provider. Eg , Such as Microsoft.

Webex will prompt you to allow or deny the permissions associated with your account.

...

Press accept and log back into yarnman when it redirects

...

Token details will be stored.

...

Test Connection can be pressed to verify that Yarnman can access Webex API doing by requesting a simple about me api requestAPI.

Troubleshooting Scopes

Yarnman can help validate the scopes configured in your webex Webex app

Copy the whole URL from webexWebex

...

Press Validate Scopes in Yarnman

...

Paste the URL in the popup from Yarnman.

...

Press validate, and Yarnman will advise the roles that need to be checked on the webex Webex app

...

Troubleshooting Webex login

Where possible its , it's best to use an a Private/Incognito session to preform perform the oAuth flow. As there There could be issues with cached logins with SSO , or the wrong SSO id ID being prompted and , causing the oAuth to fail with a change of UserID midsession.

...

Troubleshooting Connectivity

The For the Oauth Flow to Work Correctly, the Web browser you use needs to be able to get access to webex Webex (internetthe Internet) and yarnman , for the oauth flow to work correctlyYarnman.

DNS

Below shows the yarnman server is not able to resolve the DNS

Code Block
yarnman@ym-ph4-wxc-glen [ ~ ]$ curl "https://webexapis.com" -I curl: (6) Could not resolve host: webexapis.com yarnman@ym-ph4-wxc-glen [ ~ ]$

...

Code Block

yarnman@ym-ph4-wxc-glen [ ~ ]$ cat /run/systemd/resolve/resolv.conf 
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 10.0.0.1
search lab.yarnlab.io

to change the dns DNS servers, in this example, we are adding replacing the single dns DNS server with multiple dns DNS servers

You will need to first login must first log in as the root user to modify system settings , using su. exit out from the root when you are done