Resource wizard: Object type credentials
|
Since 4.9
This functionality is available since version 4.9.
|
Credentials allows you to define mappings for credentials, e.g. passwords.
Configuration for credentials contains similar panels as for activation, but contains only one kind of mapping and doesn’t contain any predefined mappings. Use the credentials mappings to either pass or generate the password.
The as is mappings are very simple as midPoint implies that the password will be passed from midPoint user password to resource object password (if supported by the resource and connector) or vice versa.
|
Figure 1. Configuration of credentials
Each mapping also allows setting Lifecycle state.
This can be used during Simulations, e.g. specifying lifecycle state as Proposed will be used only to simulate the credentials mapping, Draft disables the credentials mapping etc.
Click btn:[Save settings] when done to return to the previous page from which you started the credentials editor.
| You don’t need any credentials mappings if you are not managing the passwords in the resource (e.g. if you are using SSO with another system). |
Configuration of resource wizard panels
Some wizard panels are configurable, for more information see Wizard panels.
How to use Lifecycle state
Resource, object type, attribute, mapping, synchronization situation and other aspects of resource configuration can be configured in different lifecycle states.
As it was mentioned earlier, the Lifecycle state property can be used with Simulations.
The resource is created in Proposed lifecycle state by default, it won’t work for normal deployment without switching to Active state.
By using the lifecycle state Proposed, you can test (simulate) the configuration without causing any damage to your target system data.
When the simulation results are satisfactory, you can switch the lifecycle state to Active.
As the lifecycle state can be set on various configuration items, midPoint gives you a way of turning on specific parts of configuration incrementally.
For example, after you switch your resource to Active lifecycle state, we recommend to add any new mappings first in Proposed lifecycle state.
The new mapping can be simulated without causing any harm and switched to Active lifecycle state when ready.
See also:
Limitations
Resource wizard has several limitations as of midPoint 4.8, such as:
-
expression editor supports
As is,Script,LiteralandGenerateexpressions only -
mapping ranges are not supported
-
mapping domains are not supported
midPoint resource wizard won’t be able to show or allow editing of these features but should tolerate them and keep them in the configuration.
Was this page helpful?
YES
NO
Thanks for your feedback