Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Credentials & Tidal
22-06-2015, 03:36 PM
Post: #6
RE: Credentials & Tidal
The renderer is expected to be provided with login info from the CP once and once only. After this, the renderer is expected to store its login info on disk.

The CP calls Get() on startup to decide whether the renderer already has login info. Non-empty return values for both username and password signify that the renderer does already have login info.

I'm certain that this can be made to work - we have two codebases that do exactly this Smile.

Based on the callstack you posted, I have a guess about the cause of the crash you're seeing - does your Credentials service return a valid RSA public key as its PublicKey state variable? This is required to allow Kazoo to encrypt the password before passing it via Set().
Find all posts by this user


Messages In This Thread
Credentials & Tidal - Josef - 22-06-2015, 12:05 PM
RE: Credentials & Tidal - simonc - 22-06-2015, 12:24 PM
RE: Credentials & Tidal - Josef - 22-06-2015, 12:42 PM
RE: Credentials & Tidal - simonc - 22-06-2015, 02:16 PM
RE: Credentials & Tidal - Josef - 22-06-2015, 02:47 PM
RE: Credentials & Tidal - simonc - 22-06-2015 03:36 PM
RE: Credentials & Tidal - Josef - 22-06-2015, 04:05 PM
RE: Credentials & Tidal - simonc - 22-06-2015, 07:15 PM
RE: Credentials & Tidal - Josef - 22-06-2015, 08:00 PM
RE: Credentials & Tidal - simonc - 22-06-2015, 09:11 PM
RE: Credentials & Tidal - Josef - 22-06-2015, 10:09 PM
RE: Credentials & Tidal - simonc - 23-06-2015, 12:44 PM
RE: Credentials & Tidal - Josef - 23-06-2015, 01:56 PM
RE: Credentials & Tidal - simonc - 23-06-2015, 01:59 PM
RE: Credentials & Tidal - Josef - 23-06-2015, 02:06 PM
RE: Credentials & Tidal - simonc - 23-06-2015, 02:52 PM
RE: Credentials & Tidal - Josef - 23-06-2015, 04:46 PM

Forum Jump: