# Authorisation with JWT Provider

**URL:** https://community.hivemq.com/t/authorisation-with-jwt-provider/611
**Category:** HiveMQ Extensions
**Created:** [June 25, 2021, 2:06pm UTC](https://community.hivemq.com/t/authorisation-with-jwt-provider/611 "2021-06-25T14:06:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![CanD](https://avatars.discourse-cdn.com/v4/letter/c/59ef9b/32.png) [@CanD](https://community.hivemq.com/u/CanD)
#### Post date: [June 25, 2021, 2:06pm UTC](https://community.hivemq.com/t/authorisation-with-jwt-provider/611/1 "2021-06-25T14:06:45Z")

</div>

Hi,

I was able to connect ESE with our Authorisation Server supporting the OAuth Client credential grant.

1. I found that the simple-auth for the “jwks-endpoint” wasn’t working. I had to disable basic auth on the jwks API so that ESE could retrieve the public key. Should simple-auth working with basic auth?

2. Is it possible to have an authentication manager which is working with scopes so that I can give various client different scopes and define to which topics wildcards these clients can subscribe and publish based on the scope? And preferable without a additional DB setup? Is this possible in ESE or do I have to use the Extension SDK for that?

This is my current configuration:

\<?xml version="1.0"?\> cts-provider true http://localhost:9015/cts/token/keys 1800 hivemq mqtt cts-provider 300 ${mqtt-clientid} com.sap.cts topic\_subscribe