ILLiad Ideas
29 results found
-
SAML multiple attributes (allow for multiple and to list those which are allowed)
We have come to understand that ILLiad's SAML module does not support SAML2 attributes sent by the Identity Provider with multiple values. These would take the basic form in the SAML assertion XML like:
<saml:Attribute Name="multiAttributeName">
<saml:AttributeValue>Value 1/saml:AttributeValue
<saml:AttributeValue>Value 2/saml:AttributeValue
<saml:AttributeValue>Value 3/saml:AttributeValue
/saml:AttributeIt is described on pg 31 of the spec https://www.oasis-open.org/committees/download.php/56776/sstc-saml-core-errata-2.0-wd-07.pdf#page=31
As this is a common method of delivering data structures inside of SAML attributes especially when specifying items like user affiliations or group memberships, we request that support be added in the future to read and operate on multi-value/list attributes within the RemoteAuthValidation table.
2 votes -
Fix the "Illiad Authentication" Checkbox so it Does not Automatically Enable itself when Saving a New User Record
Leaving the ILLiad Authentication checkbox unchecked/unchanged when creating a new user will default the user to ILLiad Authentication type.
Leaving the "ILLiad Authentication" checkbox unchecked/unchanged while creating a user in the Client still defaults to ILLiad Authentication when the user is created, even though the option is not checked when saving. This bug has been around for awhile with no fix in sight. Can this please be addressed in a future Illiad release? No one can remember to go back and uncheck that box constantly.This is currently logged as Bug# 12841
15 votes -
Ability to COPY and PASTE in User notes field
This will allow us to copy and paste notes when we are merging accounts or when we need to copy and paste notes to multiple accounts (within families, etc.)
2 votes -
Transfer User Notes when merging users
When an existing user account is merged with an new one, in addition to moving the open requests, we would like any User Notes to be moved as well. We use these notes to track various issues with patron accounts and right now staff are manually copying each note.
17 votes -
staff manager
We know this exists in the Aeon staff manager, but don’t see a way to do so in ILLIad. This is a functional gap between the two products.
We would like to be able to display the Description field in the columned display. We find it useful when reviewing staff accounts in order to address staffing changes, etc.
1 vote -
3 votes
-
Make sure all accounts that log in with past Expiration Dates must go through the Expired Users page and update their information
Users with old expired stub accounts are not prompted to update their information when logging into their ILLiad accounts again. The account status goes from Cleared=NEW to Cleared=NO, and ExpirationDate isn't checked/updated because the account was technically already created.
We need ILLiad to check whether an account is expired or overwriting an existing expiration date. Having a patron from 2012 able to submit requests without updating their contact information or preferences is a real problem for us -- patrons can and do change their email addresses, and we allow patrons to choose to have loans delivered to their home if…
2 votes -
Allow for different error messages based on response from LDAP server
This would allow site administrators to configure different status line responses for login attempts based on the LDAP error response so that patrons can know if they had invalid credentials or exceeded login attempts.
1 vote -
Gray out notification methods not selected
Gray out Email Notifications and SMS Notifications checkboxes (on the User form) if the selected Notification Method is Mail or Phone
0 votes -
1 vote
-
Encrypt Passwords in Customization Manager
Having an email password in plain text available to anyone with Customization Manager rights is a security risk.
3 votes -
User expiration by status
Ability to control user expiration based on User status i.e. I don't want Faculty accounts to expire. Or only expire undergraduate accounts.
6 votes -
Clear browser cache
Grant us the ability to clear previously entered browser data and the web cache within the "Docline request web browser window" in the illiad client, perhaps at the very least add a back button?
This lack of functionality can be particularly problematic with Docline's new multipath sign-on feature. A user in the illiad client could enter a "valid" login, like say their facebook, google, or institution's SSO credentials, which would pass thru the gateway, but still wouldn't be authorized with Docline. Locking them out docline but having no easy way to change their credentials to the "correct" login.
So far…
1 vote -
Account History Details
It would be nice to see a User History tab on their User window. For example, what link did they come from to create an account, what time stamp they entered Users to Clear, transfer history, etc.
3 votes -
Add a way to reveal what you type in the password change box
Add a way to reveal what you type in the password change box so staff can make sure they have typed in what they think they've typed in.
4 votes -
Ability to suspend patron from loans while still allowing requests for article copies.
We have users who cannot be trusted with book loans, but I still want them to be able to request articles. I'd like a way to block loans but not articles.
46 votes -
Allow API to update existing users
This is similar to the request to "update user account by pulling user data from org directories via Single Sign on"
9 votesCorrection: The API supports creating users but not updating existing users. We are reviewing this request.
-
Allow Database Manager To Run on a Schedule
We would like to be able to run Database Manager tasks on a schedule. For example, we would like to flip expired patrons to blocked on a nightly basis instead of requiring interaction from staff.
2 votes -
I'd like to have the power to make mass changes such as changing Department Names.
example: Our Political Science department changed their name. I want to be able to make this change to all the existing patrons it would apply to.
20 votes -
Allow API to Add, Remove, and Update records in the UserValidation table
Stanford U is locally hosted and has a custom job that imports users directly into the Users table. This job will update users based on any change event triggered in the Registrar's database. It creates many users that never end up using ILLiad. We would like a standard method of creating a process that pushes users into the UserValidation table and can update users, regardless of their being in the Validation table or in the Users table.
8 votes
- Don't see your idea?