SAML SSO error

1
I can’t Figure this error out… had no message but this is the stack trace. Any help would greatly be appreciated. java.lang.IllegalArgumentException: requirement failed: Ids should not be null     at scala.Predef$.require(Predef.scala:337)     at com.mendix.basis.component.DataStorageCore.retrieveId(DataStorageCore.scala:19)     at com.mendix.basis.component.DataStorageCore.retrieveId$(DataStorageCore.scala:17)     at com.mendix.basis.component.InternalCore.retrieveId(InternalCore.scala:21)     at com.mendix.basis.session.PersistentSession.<init>(PersistentSession.scala:40)     at com.mendix.basis.session.PersistentSession.<init>(PersistentSession.scala:45)     at com.mendix.basis.session.SessionManagerBase.createPersistentSession(SessionManagerBase.java:236)     at com.mendix.basis.session.SessionManagerBase.getSessionById(SessionManagerBase.java:157)     at com.mendix.basis.component.SessionCore.getSessionById(SessionCore.scala:43)     at com.mendix.basis.component.SessionCore.getSessionById$(SessionCore.scala:43)     at com.mendix.basis.component.InternalCore.getSessionById(InternalCore.scala:21)     at com.mendix.core.Core.getSessionById(Core.java:1448)     at saml20.implementation.security.SessionManager.evaluateActiveSessions(SessionManager.java:598)     at saml20.implementation.security.SessionManager$1.run(SessionManager.java:184)     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)     at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)     at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)     at java.base/java.lang.Thread.run(Thread.java:834)  
asked
1 answers
0

I had similar issues where this error was thrown every minute. Restarting this app didn't seem to fully resolve the issue. 

What happened was that a user's account was deleted while the user was logged in and having a active session. The session somehow remained existing without an associated account. Adding an active sessions grid to the user management page we could delete this session as well, which seemed to resolve the problem. 

 

answered