| ... |
... |
@@ -1,9 +1,11 @@ |
| 1 |
|
-This feature is subject to costs and available from {{formcycle/}} version 6.4 onwards. It allows the usage of external identity providers for the authentication of users in {{formcycle/}} forms. |
|
1 |
+This feature is subject to costs and it allows the usage of external identity providers for the authentication of users in {{formcycle/}} forms. |
| 2 |
2 |
|
| 3 |
3 |
|
| 4 |
4 |
{{content/}} |
| 5 |
5 |
|
| 6 |
|
-{{figure image="identity_provider_en.png" clear="h1"}}Configuration interface while adding a new Identity Provider.{{/figure}} |
|
6 |
+{{figure image="identity_provider_en.png" clear="h1"}} |
|
7 |
+Configuration interface while adding a new Identity Provider. |
|
8 |
+{{/figure}} |
| 7 |
7 |
|
| 8 |
8 |
It is possible to configure identity providers here, which can be used to authenticate users in all forms of all [[clients>>doc:Formcycle.SystemSettings.UserInterface.Clients]]. If an identity provider is only supposed to be available in certain clients, it can be configured in the [[User settings>>doc:Formcycle.UserInterface.UserSettings.ExternalUsers.WebHome]] instead. |
| 9 |
9 |
|
| ... |
... |
@@ -12,10 +12,11 @@ |
| 12 |
12 |
By clicking on the {{ficon name="plus-circle-outline"/}} button in the upper left corner, a new Identity Provider can be created. At first 4 buttons appear, by which the type of identity provider must be selected. The following types of Identity Providers are available: |
| 13 |
13 |
|
| 14 |
14 |
* [[OpenID Connect>>Formcycle.SystemSettings.UserInterface.ExternalUsers.openid]] |
| 15 |
|
-* [[OAuth 2 >> ]] |
|
17 |
+* [[OAuth 2 >>Formcycle.SystemSettings.UserInterface.ExternalUsers.oauth]] |
| 16 |
16 |
* [[SAML 2.0>>Formcycle.SystemSettings.UserInterface.ExternalUsers.saml]] |
| 17 |
17 |
* [[Facebook>>Formcycle.SystemSettings.UserInterface.ExternalUsers.facebook]] |
| 18 |
18 |
* [[Google>>Formcycle.SystemSettings.UserInterface.ExternalUsers.google]] |
|
21 |
+* [[Azure AD >>Formcycle.SystemSettings.UserInterface.ExternalUsers.azure]] {{version major="7" minor="1" /}} |
| 19 |
19 |
|
| 20 |
20 |
The individual options for configuring these identity providers are described in detail on the linked subpages. |
| 21 |
21 |
|
| ... |
... |
@@ -25,4 +25,4 @@ |
| 25 |
25 |
|
| 26 |
26 |
== Use data of the logged in user in forms == |
| 27 |
27 |
|
| 28 |
|
-The user data returned upon login can be used, among other things, to fill form fields. For this purpose, the placeholders [[[%$USER%]>>doc:Formcycle.UserInterface.Variables.WebHome||anchor="sec_user_variables"]], [[[%$LAST_USER%]>>doc:Formcycle.UserInterface.Variables.WebHome||anchor="sec_user_variables"]] and [[[%$INITIAL_USER%]>>doc:Formcycle.UserInterface.Variables.WebHome||anchor="sec_user_variables"]] can be set as values in form elements. Alternatively, this data can be accessed in JavaScript through the XFC METADATA object {{jsdoc page="metadata" name="user"/}}. |
|
31 |
+The user data returned upon login can be used, among other things, to fill form fields. For this purpose, the placeholders [[[%$USER%]>>doc:Formcycle.UserInterface.Variables||anchor="sec_user_variables"]], [[[%$LAST_USER%]>>doc:Formcycle.UserInterface.Variables||anchor="sec_user_variables"]] and [[[%$INITIAL_USER%]>>doc:Formcycle.UserInterface.Variables||anchor="sec_user_variables"]] can be set as values in form elements. Alternatively, this data can be accessed in JavaScript through the XFC METADATA object {{jsdoc page="metadata" name="user"/}}. |
