Skip to main content
Nintex Community Menu Bar
Solved

K2 Five Realm

  • August 13, 2018
  • 2 replies
  • 28 views
  • Translate

I already have a realm that connect to a designer using this url (https://dewi.cimbniaga.co.id/Designer) and already check the database that the url has been added.

 

16972i37511A3434CC3643.png

Best answer by boringNerd1

Hi,


The URL must actually lead to the actual site and page. On the server that is hosting your Designer, open IIS Manager, right-click on your K2 site, and select Edit Binding. Make sure there is a binding for dewi.cimbniago.co.id.


 


If you want users to be able to use that URL as well, then make sure in your DNS, you have a record that points dewi.cimbniaga.co.id to your web server.


 


And I am not sure if your realm and audience settings are correct. Usually my environment has 1 audience URI that matach to 1 realm URI. I recommend you delete 'https://dewi.cimbniaga.co.id/Designer' audience URI, and create a new realm for https://dewi.cimbniaga.co.id/Designer.

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+15
  • 498 replies
  • Answer
  • August 13, 2018

Hi,


The URL must actually lead to the actual site and page. On the server that is hosting your Designer, open IIS Manager, right-click on your K2 site, and select Edit Binding. Make sure there is a binding for dewi.cimbniago.co.id.


 


If you want users to be able to use that URL as well, then make sure in your DNS, you have a record that points dewi.cimbniaga.co.id to your web server.


 


And I am not sure if your realm and audience settings are correct. Usually my environment has 1 audience URI that matach to 1 realm URI. I recommend you delete 'https://dewi.cimbniaga.co.id/Designer' audience URI, and create a new realm for https://dewi.cimbniaga.co.id/Designer.

Translate

Forum|alt.badge.img+9
  • 146 replies
  • August 13, 2018

Hi NovaCammy


 


You will have to create an entry in the ClaimRealm table for the new URL, and also make sure that in the ClaimRealmIssuer table that your Issuer and Realms link up.


If not done, just make sure you have the URL entry in the binding in IIS.


 


-Jean

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings