Symptoms
After the SSL certificate and DNS alias was changed by K2 Support engineers from https://servername/ to https://k2.domain.com, SSL warnings appear when users are redirected to the logon URL.
Diagnoses
The URLs need to be updated in the following tables:
Identity.ClaimIssuer
Identity.ClaimRealm
Identity.ClaimRealmIssuer
Identity.ClaimAudience
Resolution
Please open these Forms:
https://k2.domain.com/Runtime/Runtime/Form/Manage Issuers/
and edit both entries' URI to point to the new server name - k2.domain.com
https://k2.domain.com/Runtime/Runtime/Form/Manage Site Realms/
and either edit or add new entries for all three items - ViewFlow, Designer and Runtime - to point to the new server name. Make sure the Audiences are also correct!
Lastly, it would probably be a good idea to remove the entries in the Environment Library in K2 Workspace that still point to the old K2 server, just to be on the safe side. Or at least make doubly sure that none of them are active / set as default. It seems that a lot of Connection Strings (like Category Server or SmartForms Server) still point to the hostname instead of the FQDN. It's your decision whether you want to keep it this way, but just make sure that all the SmartForms entries point to the correct URL (for example, "SmartForms Designer Runtime" or just "SmartForms Runtime").
After you have made the changes above and restarted the K2 Service, it should not redirect to the old hostname URL when authenticating with /Identity/
------------------
Just as a note, perhaps this may be helpful to someone one day: I first changed the existing realm URL entries - this caused an error ("No realm for URL 'https://servername/Runtime/' found") to Pop up whenever one tried to Access a runtime URL. Adding the original entries (the ones complained about in the error) in addition to the changed ones didn't work out. Only changing back the original entries to the old URL and adding new entries for the DNS alias made it work. Probably there are some references on database GUIDs in the Background that caused this behaviour.
