Last modified on 25 March 2020, at 13:11

Authenticate (Activity)

Revision as of 13:11, 25 March 2020 by NNE (Talk | contribs) (Description)

This activity pushes a single content object to UBIK® Push service participants.


[edit]

Description

Authenticate
Name Authenticate
Purpose Push a single object
Category UBIK Stuido
Returns true if successful
Version 2.6.4

Arguments

Argument Type Direction Purpose
Application String In
AuthenticationResult AuthenticationResult Out A valid Authentication Token, be aware, that these kind of tokens are only supported for short period of Time.
Context String In
DisplayName String In Name of the File
Geo GeoInformation In Location (Latitude, Longitude, Altitude)
Login String In The Login Object holds the necessary information for managing logins to UBIK®, each Login name must be unique.
Manufacturer String In Computer Manufacturer, e.g., HP, DELL and and so forth
Model String In Computer model, e.g., Pavilion, Inspiron and and so forth
OperatingSystem OSTypes In An operating system (OS) is system software that manages computer hardware, software resources, and provides common services for computer programs.
Password String In A password, sometimes called a passcode, is a memorized secret, string of characters including letters, digits, or other symbols, used to confirm the identity of a user
Result Boolean Out
Satellite String In
ServiceVersion String In
USAMUrl String In Combination of Authentication Server and Authentication Service Path


Usage

Use this activity to push a single object to certain UBIK® Clients. The criterions to which clients the object should be actually pushed can be defined with subsequent PushCriterion activities. It is a nestable activity, which means it can host any amount of sub-activities that will be processed sequentially. The hosted activities are typically Push criterions like PushCriterionLogin, either as direct children but also wrapped within looping activities like ForEach or While.


Example

See also