Hello,
we have been experiencing problems with publishing K2 on WAP.
We created a https binding on the iis and HTTPS/k2server.domain.hr SPNs on the k2 service user. The K2 service user in AD has the "Trust for delegation to any service" option selected. On ADFS we created a non-claims relying party trust with the url https://k2server.domain.hr. We than published the url on the WAP server.
The preauthentification method that is used is ADFS and the WAP servers have delegation to HTTPS/k2server.domain.hr. Internally, k2 has Windows, negotiate as an auth method.
This setup has worked for a week and than suddenly stopped working. When we try to connect to the published url, sts login site is presented, we type our username and password and the k2 site returns an HTTP 500 error. No changes have been made. The same thing happend when we added a claims based trust in ADFS - it worked for a week and than stopped working out of the blue. That is why we changed the trust to non-claims.
We republished the site and now it works but it's a matter of time when it stops working. Also, how can we publish the site so that the K2 app works?
Best regards.