+18Getting kicked out of Jamf Pro server. If you are experiencing a similar issue here is my ticket number: 19843077
After enabling the SSO I am getting kicked out of the Jamf server multiple times daily.
Behavior:
clicking on a link presents signed out page
or
actively browsing a page and presented singed out page
Browser:
Safari
Chrome
OS: 15.4 (scheduled the update for later in the week)
+18Submitted to support:
Jamf Log with debug
Chrome .har file
+25
+18I’m using the SSO for Jamf account, not an IDP.
+25My condolences. IMO Jamf’s decision to require Jamf Account SSO for the Blueprints and Compliance Benchmarks feature was an extremely poorly conceived decision. My org’s team responsible for SSO systems has no interest in supporting integration between the system we’re already using for SSO with Jamf Pro and Jamf Accounts SSO so features that I really would like to utilize now, and will require for properly managing macOS Tahoe and later, are currently unusable.
+13
+18Support tells me one or more of the database tables are at 2GB in size and want me to clear logs again and possibly have a shorter window for logs.
I did this earlier in the week, and it caused mobile devices not be be able to enroll for remainder of the day.
Am I wrong to say that Jamf needs to allocate more resources to the node then? or not offer management history to be 6 months as an option?
Looking at this document: https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/Log_Flushing.html
“Flushing logs reduces the size of the database and can speed up searches.”
it does not mention logout timeouts.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.