Allison Erhardt
My feedback
7 results found
-
57 votesAllison Erhardt supported this idea ·
-
327 votesAllison Erhardt supported this idea ·
-
22 votesAllison Erhardt supported this idea ·
-
180 votes
Hi,
The login for an account that is managed in an external IdP (such as a Shibboleth IdP), is done by the IdP and not by Alma. Alma does not control the success of this type of login.
Alma does control the login status if the user record is internal, i.e. its password is managed in Alma. In that case, we will indeed allow the login to succeed even if the user is expired.
The user record status will be verified when calculating:
- GetIt services (hold/digitization/resource sharing)
- My Account renew loan option
In either case, the account will be considered active only if:
- The user record status is active
- The user record expiry date is not in the past
- The user’s patron role is active
- The user’s patron role’s expiry date is not in the past
The login, however, will not be affected by these conditions.
Thank you,
MosheAllison Erhardt supported this idea · -
134 votesAllison Erhardt supported this idea ·
-
70 votes
An error occurred while saving the comment Allison Erhardt supported this idea · -
53 votes
After reviewing this idea, Alma Product Management has decided to update our development plans to include this suggested change. Thank you for your contribution
Allison Erhardt supported this idea ·
Also, the library location is included in the XML, but not what library that location belongs to! Including the Library would be of great help. current a code (that I cannot find a map for) is sent, but it is a behind the scenes number, and not the code we create for the Library.