The user management component is very useful, and we hope to use it along with the ignition auto datasource to save lots of time in developing our own user management.
However, there are a few custom fields we would like to add to the user, so we have created another table (lets call it custom_props) that is keyed to the user id in the auto generated (lets call it auto_users) table. However, in order to key off the auto_users table we need to create the user first.
What we initially came up with is creating a popup window with first name, last name, username, and password options. This window inserts the user manually to the auto_users table bypassing the user management component. We also have our custom properties here that are inserted after the user is manually inserted.
However, we have the user management component in a window with a list of the users fetched to the database. The selected username in the list is bound to the user management “Username” field of the user management component. The mode is set to edit single.
This works brilliant. Our user is inserted manually and our meta data is inserted to the custom_props table. It immediately appears in our selection list, however if we select the user in our list that updates the Username property of the Edit Single user management component, there is about a 10-15 second delay before it will accept the username as valid. The username also doesn’t show up on the user page in the gateway managment webapp.
A couple questions:
- Is there a script/service that is running periodically that is doing something to make the users editable in the user management component? Can we call this on our manual insert to “refresh” the users?
- Is there a better suggested way to add a few custom fields to an auto user source?
- Can we use the user management component with a manual user source if we configure our database correctly and should we abandon this whole auto user source with custom properties idea to pursue this method?
Any brainstorming/feedback would be appreciated.
UPDATE: We just found the “Cache Validation Timeout” property on the user source config that dictates how often the user source is updated, we dropped this down to 1 second. This doesn’t seem to do anything though.