3scale doesn't support 2 different applications on different SSO realms with the same clientID, but with different secrets:

• Creating 2 different Applications 
• for 2 different Products 
• with 2 different Secrets 
• but with the same clientID 
• using API Docs (Create Application endpoint)

In this scenario, after creating the 2nd application, the client credentials on RH-SSO shows the same secret from the 1st application. 

Observations: 

• We have detected on zync pod --> zync_production database --> clients table:
  • Two records with the same client_id value ("sso-client-sync-test") and different id values [it seems to be correct and obeying clients table PK (id, client_id)]
• We have detected on system-mysql pod --> system database --> application_keys table:
  • One record with "secretA" for field value [with the application_id FK field pointing to the correct id of the cinstances table (it also seems to be correct)]
  • One record with "secretB" for field value [with the application_id FK field pointing to the correct if of the cinstances table (it also seems to be correct)]

Additional Scenario: 3scale overrides the value of the client in the incorrect realm

• Create ProductA connected to RealmA
• Create ProductB connected to RealmB
• Create an application in ProductA
• Create an application in ProductB using API Docs (Create Application endpoint) with the same clientID and clientSecret but different name and description

In the scenario, after creating the second application (ProductB), the name and description of the client in RealmA may be overridden with the new values which should have been written to RealmB