XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • 1.1.x
    • 1.1.3.Final
    • Gateway API
    • None
    • Hide

      Reproducing the problem is not straightforward, but i would say the best thing is to setup an environment and keep it running , then give it some traffic to call apiman-gateway services .. after a while you will start receiving "Token is not active"

      Show
      Reproducing the problem is not straightforward, but i would say the best thing is to setup an environment and keep it running , then give it some traffic to call apiman-gateway services .. after a while you will start receiving "Token is not active"

      After some traffic on the server, with issuing tokens and hitting services, and wildfly running for a while, the apiman-gateway starts to act weird . only sometimes , it starts with 1/10 calls failed with "Token is not active" and keep increasing .. the only fix was for me to restart server , and it seems to be working after that.

      Marc helped me and created a version of the keycloak policy plugin to print out logs , and i found out that the apiman is sending old tokens to keycloak , and that's why keycloak is returning "Token is not active" .

              msavy_jira Marc Savy (Inactive)
              fadiabdeen Fadi Abdin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: