cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1500
Views
0
Helpful
5
Replies

webex CC redirect after logout

eleveo1
Level 1
Level 1

We are trying to implement WebexCC as identity provider.
We are able to use endpoints from documentation page https://developer.webex-cx.com/documentation/authentication for authorizing user and obtain access token, however we found nothing about logout anywhere in the documentation.

For logout we tried https://webexapis.com/v1/logout however it first requires access token in the header, but when it is provided, it responds with HTTP 404. Then we found https://idbroker.webex.com/idb/oauth2/v1/logout which worked for us, however it gets stuck on "You are signed out." page and we would like to be redirected back to our application. We also tried to add parameters to this logout url like "redirect_uri" or "post_logout_redirect_uri" but it does nothing and we also tried parameter "goto=ourApplicationUrl" however it responded with "returnURL is not allowed".

So I would like to ask:
1. is there some documentation for logout endpoint?
2. is there a possibility to do redirect back to our application after logout?

Thanks

2 Accepted Solutions

Accepted Solutions

Hi @eleveo1 

This is how to achieve it: 

URL : 

Accepts : POST, GET

POST https://idbroker.webex.com/idb/oauth2/v1/logout?goto=https%3A%2F%2Fwww.eleveo.com%2F 

Needs: Bearer Token Authorization Header OR access token in URI params.

goto= Needs: URI encoded website string

Working Example:

 

https%3A%2F%2Fwww.eleveo.com%2F

https://www.eleveo.com was added as Redirect URI on the App Settings.

Here is the 200 OK after redirect and logout - 

Screen Shot 2022-07-11 at 2.53.05 PM.png

View solution in original post

Arunabh Bhattacharjee
Cisco Employee
Cisco Employee

Attaching additional documentation around this. Have asked the team to add this to the documentation. Screen Shot 2022-07-11 at 10.09.10 AM.png

View solution in original post

5 Replies 5

Yeah, I’ve not seen this API in the documentation either. I would reach out to the BU for clarification or open a case with DevNet to see if they can track down the right person to assist.

 

david

Arunabh Bhattacharjee
Cisco Employee
Cisco Employee

Hi @eleveo1 , this is more of a Control Hub Login/Logout query but I will attempt to provide an answer,

could you please try the parameters ?type=logout&goto=https://eleveo-example-website.com

 

but with the idbroker URL i.e this is how one can logout and redirect to the desktop website: 

GET https://idbroker.webex.com/idb/saml2/jsp/doSSO.jsp?type=logout&goto=https://desktop.wxcc-us1.cisco.com

 

Testing this on postman invalidates the token passed in the Auth header and logs out the user, along with redirecting the user to the targeted site.

 

Let me know if this helps.

 

Thanks,

Arunabh.

hello @Arunabh Bhattacharjee 

thanks for your reply, however it does not work.

 

When I call: GET https://idbroker.webex.com/idb/saml2/jsp/doSSO.jsp?type=logout&goto=https://our-example-website.com

 

I get response: returnURL is not allowed.

 

Of course https://our-example-website.com is replaced with real working url and also, this url is added in "Redirect URI(s)" section when I register our app on developer.webex.com/my-apps. I also tried to add clientId parameter, but does not work either.

From my observation I noticed that goto parameter only works for ".cisco.com" URLs, so this does not help us.

 

Hi @eleveo1 

This is how to achieve it: 

URL : 

Accepts : POST, GET

POST https://idbroker.webex.com/idb/oauth2/v1/logout?goto=https%3A%2F%2Fwww.eleveo.com%2F 

Needs: Bearer Token Authorization Header OR access token in URI params.

goto= Needs: URI encoded website string

Working Example:

 

https%3A%2F%2Fwww.eleveo.com%2F

https://www.eleveo.com was added as Redirect URI on the App Settings.

Here is the 200 OK after redirect and logout - 

Screen Shot 2022-07-11 at 2.53.05 PM.png

Arunabh Bhattacharjee
Cisco Employee
Cisco Employee

Attaching additional documentation around this. Have asked the team to add this to the documentation. Screen Shot 2022-07-11 at 10.09.10 AM.png