5 Replies Latest reply on Mar 10, 2017 7:38 AM by Luis Vazquez

    Spark SSO relogin errors after Windows 10 lock out.

    Johnny

      Hi all,

       

      An Openfire SSO has been setup using examples from  28 Steps to Single Sign On for Openfire XMPP Server on Windows Server 2012 R2 with Spark  and a Spark client can connect successfully to the Openfire server using SSO. However, something odd happens after Windows 10 OS decides to go into the lock screen. It seems that the Spark client cannot re-login again using SSO .

       

      Here are the debug logs shown:

      Debug is true storeKey false useTicketCache true useKeyTab false doNotPrompt true ticketCache is null isInitiator true KeyTab is null refreshKrb5Config is true principal is null tryFirstPass is false useFirstPass is false storePass is false clearPass is false

       

      Refreshing Kerberos configuration

              Acquire TGT from Cache

              Principle is null

              null credentials from Ticket Cache

      [Krb5LoginModule] authentication failed

              Unable to obtain Principal Name for authentication

       

      I then signed out of the Windows account and signed in again. After which, the Spark client can re-login using SSO. Anyone knows if this is the intended behavior?

       

      Has anyone also encountered this issue before and managed to fix it?

       

      Regards,

      Johnny.