dadkind
Apprentice

Adding server re-directs Authentication request to new server

Hello,

We've been having trouble adding additional Forms servers to our farm.

 

We have a Test server (IIS + SQL).  We are adding a new Forms server to the farm and are referencing the Test server as the SQL server for this instance.

 

After the installation, when a user navigates to the Test server instance, the user is directed to the New server for authentication. But since the new server does not have a database of it's own, the authentication is failing.

 

We can fix things by running the configuration tool on the Test server. This updates things and the Test server returns to functionaing properly (we still have not successfully configured our Forms server).

 

1. Why does the user get redirected to the New server for authentication?

2. It appears that the Application Instance or DB on the Test server is updated by the installation on the New server. Why?

 

Thanks,

Tomas

 

 

0 Kudos
Reply
3 Replies
Perc
Apprentice

Re: Adding server re-directs Authentication request to new server

Hi Tomas, 


 


Thank you for your post here. I would like to ask the following questions:


 


What version of K2 are you using here ?


 


When you added the second server did you also run the K2 set up manager for both blackpearl & smartforms ? 


 


Kind regards, 


 


Percy

0 Kudos
Reply
dadkind
Apprentice

Re: Adding server re-directs Authentication request to new server

These servers are all K2 Five. All were upgraded from 4.7.

 

We ran the K2 Setup Manager on the server in the DMZ, but have run into errors and the install does not complete.

 

Immediately following this, any requests to the original server (inside the DMZ) result with the user being re-directed to

the external server for Authentication which fails because that server can't access Active Directory.

 

Thanks,

Tomas

 

 

0 Kudos
Reply
boringNerd1
Apprentice

Re: Adding server re-directs Authentication request to new server

On your Management page, go to Authentication > Claims > Issuer, and check if the issuer URLs are correct.

0 Kudos
Reply