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
I created some users via iadmin mkuser but they do not show up in the list of users (modifying permissions, etc.). I think that restarting the service and/or syncing the database with the catalog may resolve this issue.
The text was updated successfully, but these errors were encountered:
…on the Metalnx database.
- Removed code for favorites, templates, user profiles, and bookmarks.
- Removed references to the deleted forms and user fields
- Changed UserService.findByQueryString to UserService.findByUsername as
the user name is the only field that can be queried since the other
fields were all stored in the local Metalnx database.
- Removed the database sync jobs.
This fixes issue 327 as user info is now obtained directly from iRODS.
[214][327] remove references to sync jobs
…on the Metalnx database.
- Removed code for favorites, templates, user profiles, and bookmarks.
- Removed references to the deleted forms and user fields
- Changed UserService.findByQueryString to UserService.findByUsername as
the user name is the only field that can be queried since the other
fields were all stored in the local Metalnx database.
- Removed the database sync jobs.
This fixes issue irods-contrib#327 as user info is now obtained directly from iRODS.
- Removed code for favorites, templates, user profiles, and bookmarks.
- Removed references to the deleted forms and user fields
- Changed UserService.findByQueryString to UserService.findByUsername as
the user name is the only field that can be queried since the other
fields were all stored in the local Metalnx database.
- Removed the database sync jobs.
This fixes issue #327 as user info is now obtained directly from iRODS.
I created some users via
iadmin mkuser
but they do not show up in the list of users (modifying permissions, etc.). I think that restarting the service and/or syncing the database with the catalog may resolve this issue.The text was updated successfully, but these errors were encountered: