Difference between revisions of "Deep Linking"
(→URI Scheme) |
|||
| Line 12: | Line 12: | ||
== Supported Actions == | == Supported Actions == | ||
| − | === Navigate to a specific object | + | === Navigate to a specific object === |
Navigation to a {{UBIK}} object is triggered by the deep link <code>NAVIGATE</code>, and supports the following parameters: | Navigation to a {{UBIK}} object is triggered by the deep link <code>NAVIGATE</code>, and supports the following parameters: | ||
Latest revision as of 11:03, 2 September 2022
UBIK® clients support mobile deep linking through URI schemes and parameters.
Security
To avoid bypassing the UBIK® security mechanisms with deep links, it is not possible to pass any kind of user credentials or other authentication factors through these links. Instead, a profile has to be specified by name.
- If there was already a successful authentication against this profile on the mobile device and the credentials were stored, the deep linking will happen without authentication
- If there are no stored credentials for that profile, the deep link will always end up at the Authentication screen and only after successful authentication, the deep link will be executed
URI Scheme
UBIK® clients register themselves with the scheme com.augmensys.ubik:// at the OS.
Supported Actions
Navigation to a UBIK® object is triggered by the deep link NAVIGATE, and supports the following parameters:
| Parameter | Purpose |
|---|---|
profile |
The name of the UBIK® profile |
uid |
The Guid of the object to navigate to |
Example: com.augmensys.ubik://NAVIGATE/?profile=New.Demo_V3&uid=c6d1e599-c665-408f-b4f9-bf6e64428610
