SAML1AttributeQuery is running Profile Action ReadConsentFromStorage on IdP5

[Francesco Malvezzi]

hi everybody,

on upgrading to IdP5 I noticed in the logs that the calls to 
SAML1AttributeQuery endpoint fail with the error:

2024-05-13 11:28:33,915 - 155.185.0.42 - ERROR 
[net.shibboleth.idp.consent.flow.storage.impl.ReadConsentFromStorage:70] 
- Profile Action ReadConsentFromStorage: Unable to read consent from storage
java.io.IOException: java.io.IOException: 
net.shibboleth.shared.logic.ConstraintViolationException: Storage object 
was not present in session
         at 
org.opensaml.storage.AbstractMapBackedStorageService.readImpl(AbstractMapBackedStorageService.java:336)
Caused by: java.io.IOException: 
net.shibboleth.shared.logic.ConstraintViolationException: Storage object 
was not present in session
         at 
org.opensaml.storage.impl.client.ClientStorageService.getContextMap(ClientStorageService.java:351)
Caused by: net.shibboleth.shared.logic.ConstraintViolationException: 
Storage object was not present in session
         at 
net.shibboleth.shared.logic.Constraint.isNotNull(Constraint.java:306)
2024-05-13 11:28:33,921 - 155.185.0.42 - ERROR 
[net.shibboleth.idp.consent.flow.storage.impl.ReadConsentFromStorage:70] 
- Profile Action ReadConsentFromStorage: Unable to read consent from storage
java.io.IOException: java.io.IOException: 
net.shibboleth.shared.logic.ConstraintViolationException: Storage object 
was not present in session
         at 
org.opensaml.storage.AbstractMapBackedStorageService.readImpl(AbstractMapBackedStorageService.java:336)
Caused by: java.io.IOException: 
net.shibboleth.shared.logic.ConstraintViolationException: Storage object 
was not present in session
         at 
org.opensaml.storage.impl.client.ClientStorageService.getContextMap(ClientStorageService.java:351)
Caused by: net.shibboleth.shared.logic.ConstraintViolationException: 
Storage object was not present in session

While looking a way to switch to something more supported than SAML1 
stuff, is there a workaround to let it work?

thank you,

Francesco

PS in relying-party.xml the profile sticks to the default:
  <ref bean="SAML1.AttributeQuery" />