[midPoint] midPoint User Template - Custom Forms

[Brad Firestone]

Thank you Pálos and Jason!

It's good to know this is possible.  I'll be sure to look at these 
options once I figure out the basics and get my first resources 
connected properly.
Have a great day!!
Brad

Pálos Gustáv wrote:
> Hi,
>
> or you can use this:
> https://wiki.evolveum.com/display/midPoint/Lookup+Tables
>
> and to hide or show some attributes over <item>:
> https://wiki.evolveum.com/display/midPoint/Authorization+Configuration
>
> Best regards,
>
> Gustav
>
> 2017-03-21 21:37 GMT+01:00 Jason Everling <jeverling at bshp.edu 
> <mailto:jeverling at bshp.edu>>:
>
>     As for dropdowns, you can create in your custom schema extension
>     enumerations, those are dropwdowns with hard-coded values, I
>     posted an example not too long ago. You can hide or show
>     attributes in the default user template by defining
>
>     Completely hide it:
>
>     <item>
>     <c:ref>c:theAttribute</c:ref>
>     <limitations>
>     <layer>presentation</layer>
>     <ignore>true</ignore>
>     </limitations>
>     </item>
>
>     Certain hidden:
>
>     <item>
>     <c:ref>c:theAttribute</c:ref>
>     <limitations>
>     <layer>presentation</layer>
>     <access>
>     <read>true</read>
>     <add>false</add> <!-- only hide for adding users but show during
>     modify -->
>     <modify>true</modify>
>     </access>
>     </limitations>
>     </item>
>
>     Same goes for filling in attribute automatically based on other
>     attributes such as department, that would be handled via the
>     default template also,
>
>     <mapping>
>     <source>
>     <c:path>$user/department</c:path>
>     </source>
>     <expression>
>     <script>
>     <code>'the value you want'</code>
>     </script>
>     </expression>
>     <target>
>     <c:path>anotherAttribute</c:path>
>     </target>
>     <condition>
>     <script>
>     <code>department == 'sales'</code>
>     </script>
>     </condition>
>     </mapping>
>
>     JASON
>
>
>     On Tue, Mar 21, 2017 at 2:06 PM, Brad Firestone
>     <bhotrock at gmail.com <mailto:bhotrock at gmail.com>> wrote:
>
>         Hi All,
>
>         I am just getting started with midPoint.  This seems like an
>         amazing system, but there is a huge amount of information to
>         learn.
>
>         We are planning to create many of our users in midPoint by
>         bringing them in from various resources (AD and LDAP). 
>         However, we will also need to create midPoint users directly
>         in the admin GUI.  The creation of these users will be done by
>         various different administrators, with each administrator
>         being responsible for a given "department".
>
>         We want to keep things as simple as possible for each
>         administrator, and also want to keep things as consistent as
>         possible. So I have a few questions about how to do this in
>         the "best way".
>
>         1.  Is it possible for attribute values shown in the New User
>         interface to have a drop-down list to select from valid values
>         for certain attributes?
>
>         2.  Is it possible to customize the New User interface so that
>         it only shows certain attributes that need to be filled in by
>         the administrator?  It would be nice if certain attributes
>         were either not shown (and automatically filled with the
>         appropriate department information), or at least had a
>         drop-down that only included the appropriate options for that
>         department.
>
>         I think that maybe these things can be done with custom forms,
>         but looking at the custom form documentation, I didn't see
>         drop-down options.  I also don't know if it's possible to show
>         different "New User" forms to different administrators based
>         on their department (Role?).
>
>         A different way of doing this might be to use Self
>         Registration?  But we would still want the ability to have
>         drop-down lists to select from.  One of the attributes would
>         be the department, and we would want that to be a defined list
>         of valid departments.  Once the user completes the
>         confirmation, then ideally the department admin would receive
>         a notification and approve/assign the roles, which would then
>         create the needed accounts on the various resources.
>
>         Thanks for any suggestions and information!
>         Brad
>         _______________________________________________
>         midPoint mailing list
>         midPoint at lists.evolveum.com <mailto:midPoint at lists.evolveum.com>
>         http://lists.evolveum.com/mailman/listinfo/midpoint
>         <http://lists.evolveum.com/mailman/listinfo/midpoint>
>
>
>
>     _______________________________________________
>     midPoint mailing list
>     midPoint at lists.evolveum.com <mailto:midPoint at lists.evolveum.com>
>     http://lists.evolveum.com/mailman/listinfo/midpoint
>     <http://lists.evolveum.com/mailman/listinfo/midpoint>
>
>
>
>
> -- 
> Gustáv Pálos
> Identity Engineer
> evolveum.com <http://evolveum.com/>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170327/8cb7fffc/attachment.htm>