Closed moabu closed 2 years ago
@yuremm, this issue is in MySql DB wherein the paged result query for agama flow is throwing the above error. Note for LDAP DB there is no issue. MySQL logs: mySql-env-logs.zip
MySQL Query:
LDAP testing
@pujavs thank you for last screenshot. It sheds light on the root case. Can you check if we define in agmFlow
objectClass qname
attribute. ProtoFlow
bean has this attribute:
@AttributeName(name = Flow.ATTR_NAMES.QNAME)
private String qname;
@pujavs , the problem is that default sort-by value employed in service implementation is qname
; here: https://github.com/JanssenProject/jans/blob/main/jans-config-api/server/src/main/java/io/jans/configapi/rest/resource/auth/AgamaResource.java#L74
But the "proper" value should be agFlowQname
, that is, Flow.ATTR_NAMES.QNAME
thankyou @yurem and @jgomer2001 for your comments. It's strange though that LDAP search is not throwing error and return 200 response.
I will change to useagFlowQname
, test and revert.
Request: GET on
/jans-config-api/api/v1/agama
Exception:
Comment: Remaining CRUD operations work without any issues.