Replacement of Portlet API

[Julien Gribonvald]

Hi,

I would like to know if peoples watched or even did things to replace
the portlet API when moving from portlets to new ways with REST API +
frontend.

The thing is that we need a replacement on preferencies and user-info.
For userInfo claims aren't enougth as we are limited by the header size.
Il have several usecase where users have a several informations where
it's not possible to define a limit as it can be unlimited...

I think that we can use some APIs and soffits interface. As example, for
the preference soffit have an interface, but is it working ? and can get
get as put user's preferencies ?

On the user-info side we already have api's like /api/v5-0/people/me,
but this is filtered from permissions and i don't see how we can se a
general permission that giev the rigths to the ciurrent user to get his
attributes.

On an other side the best would be to secure/define APIs with
authorization on to client_id. So a configuration to define what the
client_id can get (associating an api key to a client, and configuring
what the user attributes it can consomme).


Any ideas ? What do you think ?


Thanks

--
Julien Gribonvald
Coordinateur Technique - Volet Enseignement Supérieur et de la Recherche - Programme AVENIR(s) France 2030
Développeur Opérationnel - Service E-Éducation / Pôle Logiciels Libres - GIP RECIA