https://community.splunk.com/t5/Security/What-is-the-best-practice-for-managing-your-SAML-cache/m-p/298189#M7987 <P>There are a few ways to clean up the cache;</P> <P>i) Restart of splunk,<BR /> ii) Or run comand below;<BR /> ./splunk _internal call /authentication/providers/services/_reload -auth admin:changeme</P> <P>iii) Or hit the rest endpoint;<BR /> "| rest splunk_server=* /services/authentication/providers/services/_reload "</P> Wed, 30 Sep 2020 03:57:09 GMT anaidu_splunk 2020-09-30T03:57:09Z https://community.splunk.com/t5/Security/What-is-the-best-practice-for-managing-your-SAML-cache/m-p/298188#M7986 <P>etc/system/local/authentication.conf and etc/system/metadata/local.meta both contain many old entries of users that may no longer be using the platform. The files both get updated automatically when a new user logs in.</P> <P>On a search cluster, is there a recommended solution for removing these entries?</P> <P>My plan was just to shutdown the cluster members, removing all the cached data and restarting, but is there a less disruptive way?</P> <P>Thank you.</P> Thu, 29 Mar 2018 20:36:36 GMT https://community.splunk.com/t5/Security/What-is-the-best-practice-for-managing-your-SAML-cache/m-p/298188#M7986 pkeller 2018-03-29T20:36:36Z https://community.splunk.com/t5/Security/What-is-the-best-practice-for-managing-your-SAML-cache/m-p/298189#M7987 <P>There are a few ways to clean up the cache;</P> <P>i) Restart of splunk,<BR /> ii) Or run comand below;<BR /> ./splunk _internal call /authentication/providers/services/_reload -auth admin:changeme</P> <P>iii) Or hit the rest endpoint;<BR /> "| rest splunk_server=* /services/authentication/providers/services/_reload "</P> Wed, 30 Sep 2020 03:57:09 GMT https://community.splunk.com/t5/Security/What-is-the-best-practice-for-managing-your-SAML-cache/m-p/298189#M7987 anaidu_splunk 2020-09-30T03:57:09Z