Enabling Cavrnus Login from any Blueprint (Unreal Engine)
Cavrnus Login from any Blueprint
We provide Blueprint calls that will connect you to the Cavrnus Platform. The simplest of these is Cavrnus Login Member Flow.
You can type your server into the Optional Server field, otherwise it uses what is in the CSC Plugin Settings. Calling the above will prompt your users to log in, and will then present them with a list of available spaces to join.
If you want to force them to Authenticate as a particular User, or to join a particular Space, you can instead use the Cavrnus Login Member Flow with Config node.
Finally, if you want the user to join as a Guest, versions of both of these calls exist for Guests.
Note:
You MUST disable Connect on Start to use these blueprint nodes or C++ calls.
Note: You MUST disable Connect on Start to use these blueprint nodes or C++ calls.
Explanation: Connect on Start, a Cavrnus Login blueprint node or C++ function, and the Sign In button on the Cavrnus Configuration Panel will all trigger a Cavrnus Platform connection and login process. Please ensure you only have one enabled at a time.
Note: Any fields that are left blank will cause the Plugin to show the Widget requester specified in the CSC Settings for the user to enter that info.
Example: If the Optional Server in the Login Node is blank, the Member or Guest will first be prompted to enter their (server) Domain.
Note: A Cavrnus Space will often be filled with Properties pointing to specific paths within your application. Therefore, allowing users to just open any Space could result in them adding unwanted data to a Journal (i.e. Space) that is meant to be for a different application.
Example: One of your users has access to a Car Configurator Application which connects to the “Car Config” Space. They also have access to a Conference Room Application. Allowing them to join the “Car Config” Space from the Conference Room Application would give them a bunch of car-related Properties which their Application wouldn’t know what to do with. That is fine, as the Plugin and application will just ignore those values, but it may not be the desired behavior.
Info: Members vs Guests
Members are authorized users who have login credential on your domain. This method is recommended for controlling access to private or sensitive information.
Member accounts are persistent, and can either be given access to all Spaces, or to specific Spaces individually.
Guests can join automatically with no authentication. This is recommended for delivering an experience to a wide audience, without the need for creating and managing a large number of temporary accounts.
Guests can only join spaces which have been configured to allow guests to join. (See: Creating and Managing Spaces).
Guests can only access a Space through a Join ID or hyperlink that has been provided to them.
ON THIS PAGE
Next Steps
That’s the only change required to your level in order to connect it to a Cavrnus Space.
Next, we’ll configure the Connector to add login credentials, and specify which to which Cavrnus Space the level should connect.
Alternatively, you can read up on more advanced techniques in our Developer Guide, or make calls directly using our API Reference.