unity-idm-discuss

[Unity-idm-discuss] NullPointer in admin endpoint after update to unity 3.1.1

[Sander A. <sa....@fz...>]

Dear Krzysztof,

we started to test unity 3.1.1. After the deployment the webadmin
endpoint throws a null pointer exception (log is attached). The
exception is raised after the authentication is finished and the
content should be loaded. Was there an additional change in the config?

Best regards,
Sander
-- 
Federated Systems and Data
Juelich Supercomputing Centre

phone: +49 2461 61 8847
fax: +49 2461 61 6656
email: sa....@fz...

----------------------------------------------------------------------
-----------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Volker Rieke
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
-----------------------------------------------------------------------
-----------------------------------------------------------------------

Re: [Unity-idm-discuss] NullPointer in admin endpoint after update to unity 3.1.1

[Krzysztof B. <kb...@un...>]

Hi Sander,

W dniu 13.12.2019 o 08:55, Sander Apweiler pisze:
> Dear Krzysztof,
>
> we started to test unity 3.1.1. After the deployment the webadmin
> endpoint throws a null pointer exception (log is attached). The
> exception is raised after the authentication is finished and the
> content should be loaded. Was there an additional change in the config?

I think I understand what happened. I guess you was upgrading from 2.8.x 
to 3.1 via DB update. Is this correct? Assuming yes, we had a breaking 
change in internal representation of OAuth tokens, introduced in 3.0. 
There was no migration for it, as at the time this change was applied 
those tokens were wiped during migration. But at the same time (almost, 
actually bit after this change) we decided that oauth tokens (and all 
other) should not be wiped during migration. This is now implemented for 
DB upgrade and also for JSON migration since 3.1. But we havn't go back 
and write a migration for OAuth tokens, which started to be necessary 
after this change.

I'll prepare a hotfix migration in 3.1.3 to correct this behavior, which 
will be released very soon.

Thanks,
Krzysztof