You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Updated config
* Updated Readme
* Removed unnecessary file
* No longer set permissions in account lifecycle
* Initial release of script to grant permission
* Initial release of script to revoke permission
* Initial release of script to list permissions
* Removed versioning (is in Git commit history now)
* changed dependent properties to AD instead of AAD
* Added UsId to update fields when option is toggled
* Corrected createUser to createAccount
* Corrected $c.updateConnector
* Added remark for concurrent actions
* Formatted
* Corrected function Get-ErrorMessage
* Corrected user to account
* Only log update when fields are selected to update
* Fix: removed permissions
Permissions need to be further tested before we add this to the connector
* Fix readme typo's
---------
Co-authored-by: rhouthuijzen <r.houthuijzen@tools4ever.com>
Copy file name to clipboardExpand all lines: README.md
+32-30Lines changed: 32 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,22 @@
1
1
# HelloID-Conn-Prov-Target-AFAS-Profit-Users
2
-
|:information_source: Information |
3
-
|:---------------------------|
4
-
| This repository contains the connector and configuration code only. The implementer is responsible to acquire the connection details such as username, password, certificate, etc. You might even need to sign a contract or agreement with the supplier before implementing this connector. Please contact the client's application manager to coordinate the connector requirements. |
2
+
Repository for HelloID Provisioning Target Connector to AFAS Users
| This repository contains the connector and configuration code only. The implementer is responsible to acquire the connection details such as username, password, certificate, etc. You might even need to sign a contract or agreement with the supplier before implementing this connector. Please contact the client's application manager to coordinate the connector requirements. |
| create.ps1 | Create or Update AFAS user | Optionally you can update the UserID to match the mapped convention. **Note that this is not advised as this can break certain links in AFAS. Use with care!**. Users are only created or updated when this is configured, **make sure to check your configuration options to prevent unwanted actions**. |
42
+
| enable.ps1 | Unblock and optionally update AFAS user | Optionally, you can provide additional properties to update, e.g. **"EmAd", "Upn"**. The **default example sets these with the AD values**. This action is perfomed with **entry code "6"**. For more information on the entry codes, see the [AFAS documenation](https://help.afas.nl/help/en/SE/App_Conect_UpdDsc_KnUser.htm). |
43
+
| update.ps1 | Update AFAS user | Update with the specified properties, e.g. **"EmAd", "Upn"**, etc. The **default example sets these with the AD values**. This action is perfomed with **entry code "1"**. For more information on the entry codes, see the [AFAS documenation](https://help.afas.nl/help/en/SE/App_Conect_UpdDsc_KnUser.htm)|
44
+
| disable.ps1 | Block and optionally update AFAS user | Optionally, you can provide additional properties to update, e.g. **"EmAd", "Upn"**. The **default example clears these values**, as the values have to be unique over all AFAS environments. This action is perfomed with **entry code "2"**. For more information on the entry codes, see the [AFAS documenation](https://help.afas.nl/help/en/SE/App_Conect_UpdDsc_KnUser.htm).|
45
+
| delete.ps1 | Block, remove from all groups and update AFAS user | Optionally, you can provide additional properties to update, e.g. **"EmAd", "Upn"**. The **default example clears these values**, as the values have to be unique over all AFAS environments. This action is perfomed with **entry code "0"**. For more information on the entry codes, see the [AFAS documenation](https://help.afas.nl/help/en/SE/App_Conect_UpdDsc_KnUser.htm).|
46
46
47
47
<!-- GETTING STARTED -->
48
48
## Getting Started
@@ -62,14 +62,16 @@ Please see the following pages from the AFAS Knowledge Base for more information
62
62
63
63
The following settings are required to connect to the API.
| BaseUrl | The URL to the AFAS environment REST services | Yes |
68
-
| ApiKey | The AppConnector token to connect to AFAS | Yes |
69
-
| Relation number | The relation number of the AFAS environment | Yes |
70
-
| Update User when correlating and mapped data differs from data in AFAS | When toggled, the mapped properties will be updated in the create action (not just correlate). | No |
71
-
| Update User ID if it doesn't match mapped naming convention | When toggled, the userId is updated to match the mapped convention. Note that this is not advised as this can break certain links in AFAS. Use with care! | No |
72
-
| Toggle debug logging | When toggled, extra logging is shown. Note that this is only meant for debugging, please switch this off when in production. | No |
| Base Uri | The URL to the AFAS environment REST services | Yes |
68
+
| Token in XML format | The AppConnector token to connect to AFAS | Yes |
69
+
| Get Connector | The GetConnector in AFAS to query the user with | Yes |
70
+
| Update Connector | The UpdateConnector in AFAS to update the user with | Yes |
71
+
| Create account when not found | When toggled, if the user account is not found, a new the AFAS user account will be created in the create action (only in the create action). | No |
72
+
| Update on correlate | When toggled, if the mapped data differs from data in AFAS, the AFAS user will be updated in the create action (not just correlated). | No |
73
+
| Update User ID | When toggled, the User ID will be updated if it doesn't match mapped naming convention. **Note that this is not advised as this can break certain links in AFAS. Use with care!**| No |
74
+
| Toggle debug logging | When toggled, extra logging is shown. Note that this is only meant for debugging, please switch this off when in production. | No |
73
75
74
76
### Prerequisites
75
77
@@ -91,10 +93,10 @@ When the connector is defined as target system, only the following GetConnector
91
93
The data collection retrieved by the set of GetConnector's is sufficient for HelloID to provision persons.
92
94
The data collection can be changed by the customer itself to meet their requirements.
Copy file name to clipboardExpand all lines: configuration.json
+30-10Lines changed: 30 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -22,33 +22,53 @@
22
22
}
23
23
},
24
24
{
25
-
"key": "RelationNumber",
25
+
"key": "GetConnector",
26
26
"type": "input",
27
-
"defaultValue": "",
27
+
"defaultValue": "T4E_HelloID_Users_v2",
28
+
"templateOptions": {
29
+
"label": "GetConnector",
30
+
"placeholder": "T4E_HelloID_Users_v2",
31
+
"required": true
32
+
}
33
+
},
34
+
{
35
+
"key": "UpdateConnector",
36
+
"type": "input",
37
+
"defaultValue": "KnUser",
28
38
"templateOptions": {
29
-
"label": "Relation number",
30
-
"placeholder": "12345",
39
+
"label": "UpdateConnector",
40
+
"placeholder": "KnUser",
31
41
"required": true
32
42
}
33
43
},
34
44
{
35
-
"key": "updateUserOnCorrelate",
45
+
"key": "createAccount",
46
+
"type": "checkbox",
47
+
"defaultValue": false,
48
+
"templateOptions": {
49
+
"label": "Create account when not found",
50
+
"required": false,
51
+
"description": "When toggled, if the user account is not found, a new AFAS user account will be created in the create action (only in the create action)."
52
+
}
53
+
},
54
+
{
55
+
"key": "updateOnCorrelate",
36
56
"type": "checkbox",
37
57
"defaultValue": false,
38
58
"templateOptions": {
39
-
"label": "Update User when correlating and mapped data differs from data in AFAS",
59
+
"label": "Update on correlate",
40
60
"required": false,
41
-
"description": "This will update AFAS users in the create action (not just correlate)."
61
+
"description": "When toggled, if the mapped data differs from data in AFAS, the AFAS user will be updated in the create action (not just correlated)."
42
62
}
43
63
},
44
64
{
45
65
"key": "updateUserId",
46
66
"type": "checkbox",
47
67
"defaultValue": false,
48
68
"templateOptions": {
49
-
"label": "Update User ID if it doesn't match mapped naming convention",
69
+
"label": "Update User ID",
50
70
"required": false,
51
-
"description": "Use with care! This can break certain links in AFAS. Please consult AFAS first."
71
+
"description": "When toggled, the User ID will be updated if it doesn't match mapped naming convention. Use with care! This can break certain links in AFAS. Please consult AFAS first."
0 commit comments