Hi, I'm using Universal Auth Method for Jenkins plugin. But there is a 1 problem like whatever I set limit for token use it gets expired at exactly at 10 usage. For example for 1 of token I set exactly 20 usage limit to share with the team that should not have access to staging environment, they again expired after 10 usage. I analysed codebase and see that if I don't set (0) usage limit, it will be unlimited. but I think it is a issue. I believe this can result some problems for users. Did you do it intentionally or is that a real issue? If it is I am ready to contribute this project to solve issue.

Hey @urfan.musayev Urfan, thanks for the detailed report, and for offering to help out on this! One thing I'd love to understand better first: Universal Auth actually has two separate "number of uses" limits that are easy to mix up, the Max Number of Uses on the client secret, and a separate access token num-uses limit on the identity. Which one were you setting to 20? I ask because the Jenkins plugin does a fresh login on every secret fetch instead of reusing one token, so each build (and each secret path) burns a use of the client secret, which can add up faster than expected. I couldn't find any hardcoded cap of 10 in the backend, so I'd love to pin down together where the 10 is coming from. Could you let me know which field you set, and roughly how many secret paths and builds ran before it expired? Thanks