Handling database errors

[Martin Lunze]

Hi Manuel,

in the last weeks i had similar problems when my IdP 3.3.1 trys to reach 
the database.

I also used JPAStorage for idp.session and Co, but in my case the login 
process exited at idp side after the user entered his credentials.
He wasn't passed to the SP.

I didn't had the time to search for the reason why our productive IdP 
had problems to connect to the DB.
The error only occurs after 1-2 weeks after restart of IdP and only 
while updating session-infos.

There never was a problem querying the DB for the persistentID, so i 
only switched to another StorageService for the Session-handling.

I know this is no solution for your problem, but something seems to be 
different between our IdPs.

With nice regards
Martin Lunze


On 31.08.2017 10:15, Manuel Haim wrote:
> Hi list,
>
> I am running an IdP 3.3.1 with shibboleth.JPAStorageService enabled (for
> idp.session, idp.consent and idp.artifact).
>
> However, if I switch off the database server, I can see several errors
> (javax.persistence.PersistenceException) within idp-process.log, but no
> errors are shown to the user during his/her login attempts. The user can
> authenticate, but an empty attribute set is passed to the SP.
>
> Is there a predefined way to terminate the IdP flow on database errors
> (and showing an error message to the user)? Or do I have to insert e.g.
> a context-check interceptor myself?
>
> Kind regards,
> Manuel
>

-- 
Martin Lunze
IT-Systemadministrator

Technische Universität Dresden
Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
Prozessmanagement und Controlling (PMC)
01062 Dresden

Tel.: +49 (351) 463-35881
E-Mail: martin.lunze at tu-dresden.de


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5677 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://shibboleth.net/pipermail/users/attachments/20170831/26dad21c/attachment.p7s>