# Assigning an OAuth Scope to an OAuth client timing out

**URL:** <https://techcommunity.softwareag.com/t/assigning-an-oauth-scope-to-an-oauth-client-timing-out/254327>\
**Category:** Forum\
**Tags:** oauth, oauth-scope\
**Created:** [January 6, 2022, 12:31pm UTC](https://techcommunity.softwareag.com/t/assigning-an-oauth-scope-to-an-oauth-client-timing-out/254327 "2022-01-06T12:31:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Feng\_Sian5](https://avatars.discourse-cdn.com/v4/letter/f/b19c9b/32.png) [@Feng\_Sian5](https://techcommunity.softwareag.com/u/Feng_Sian5)\
**Post date:** [January 6, 2022, 12:31pm UTC](https://techcommunity.softwareag.com/t/assigning-an-oauth-scope-to-an-oauth-client-timing-out/254327/1 "2022-01-06T12:31:33Z")

</div>

#### What product/components do you use and which version/fix level?

IS 10.3, on a QA environment

#### Are you using a free trial or a product with a customer license?

Product with a customer license

#### What are trying to achieve? Please describe in detail.

Assign an OAuth scope to a OAuth client in an IS playing as an OAuth Autorizer.

This works fine in PROD but does not work in the QA env.  
PROD and QA are almost indentical: they both are clustered, they both uses their own TSA instance.

#### Do you get any error messages? Please provide a **full error** message screenshot and log file.

No error message at all - neither on the page nor in the `server.log` or in the `wrapper.log`. The page where such assignment is done (IS Admin \> Security \>OAuth, Scope Management, Associate Scopes to Clients (`oauth-scope-client-associations.dsp`)), after clicking on the “Save Changes” button, the page just waits for a timeless seconds (for sure, more than the usual time, and then … the connection breaks.

The list of attempts:

- _performing the assignment on the other IS_ (also member of the same cluster): no change, same behavior;
- tried _different browsers_ (Chrome and Edge): no change, same behavior;
- _restarted the whole thing_ (shut down the two IS and, afterwards, shut down the whole TSA, and starting them again): no change, same behavior;

The odd thing is that this used to work before, we’ve used this in the last 15 months, and it was working, and currently I’m out of other ideas on how to troubleshoot this. Has anyone faced such issue?

---

<div class="post-metadata">

**Author:** ![Feng\_Sian5](https://avatars.discourse-cdn.com/v4/letter/f/b19c9b/32.png) [@Feng\_Sian5](https://techcommunity.softwareag.com/u/Feng_Sian5)\
**Post date:** [January 6, 2022, 1:56pm UTC](https://techcommunity.softwareag.com/t/assigning-an-oauth-scope-to-an-oauth-client-timing-out/254327/2 "2022-01-06T13:56:20Z")

</div>

I got this solved by _recreating_ the the oauth client from _scratch_ (deleting it and recreating it).

_Why this glitch happened?_ Honestly, no [thin] idea…

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 6, 2022, 1:57pm UTC](https://techcommunity.softwareag.com/t/assigning-an-oauth-scope-to-an-oauth-client-timing-out/254327/3 "2022-04-06T13:57:15Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.