<p>I am currently setting up a dex instance on our Kubernetes custer to manage the LDAP authentication. Gangway is in front of it to give us the Kube config file. It worked fine the first time.</p>

<p>Then I was trying to test to disable my account to login and deleted the refresh token. Since then Dex shows the below error:</p>

<pre><code>time="2019-09-24T08:05:19Z" level=info msg="performing ldap search ou=people,dc=comp,dc=us,dc=it,dc=com sub (&amp;(objectClass=person)(uid=swedas))"
time="2019-09-24T08:05:19Z" level=info msg="username \"swedas\" mapped to entry uid=swedas,ou=people,dc=comp,dc=us,dc=it,dc=com sub"
time="2019-09-24T08:05:19Z" level=info msg="login successful: connector \"ldap\", username=\"swedas\", email=\"Sweta.Das@gmail.com\", groups=[]"
time="2019-09-24T08:05:19Z" level=error msg="failed to delete refresh token: not found"
</code></pre>

<p>This is expected but how do I get over this ? How to restore my account?</p>

swetad90
<p>It seems like you have to delete the saved offline session as well. What is your storage options for Dex? To find out, you need to use your admin config for kubectl and check dex configmap issuing 
<code>kubectl -n &lt;DEX NAMESPACE&gt; get configmap &lt;DEX CONFIGMAP&gt; -o yaml</code></p>

<p>In case you are using <code>kubernetes</code> as storage there is an offline session (custom resource definition) associated to your account that to have to delete as well. After that you may generate and use a new kubectl configuration using gangway.</p>

<p>List offline sessions:
<code>kubectl -n &lt;DEX NAMESPACE&gt; get offlinesessionses -o yaml</code></p>
