topic Re: Why do I get "Provided token does not have permission to subscribe" after restart? in ArcGIS GeoEvent Server Questions

Why do I get "Provided token does not have permission to subscribe" after restart?

PeterGrüninger — Thu, 16 May 2019 12:22:26 GMT

I'm using GeoEvent-Server with a StreamService.

GeoEvent-Server ist federated with Portal.

I can successfully publish StreamServices and use them in Portal.

Nevertheless, everytime I restart GeoEventServer StreamServices aren't accessible any longer. In the log-File (karaf.log) you can see (among many other stuff) the following error-messages:

p965815353-923 | StreamContainer | 27 - com.esri.arcgis.discovery.arcgis-stream-container - 10.6.1 | Provided token does not have permission to subscribe.
Line 14443: 2019-05-16T14:01:50,949 | ERROR | qtp965815353-99 | StreamContainer | 27 - com.esri.arcgis.discovery.arcgis-stream-container - 10.6.1 | Provided token does not have permission to subscribe.
Line 14844: 2019-05-16T14:01:51,415 | ERROR | qtp965815353-923 | StreamContainer | 27 - com.esri.arcgis.discovery.arcgis-stream-container - 10.6.1 | Provided token does not have permission to subscribe.
Line 15154: 2019-05-16T14:01:51,660 | ERROR | qtp965815353-922 | StreamContainer | 27 - com.esri.arcgis.discovery.arcgis-stream-container - 10.6.1 | Provided token does not have permission to subscribe.

After republising the service with option "overwrite" they start working again.

This leads me to the following question:

Where does the token come from?
... where is it stored?
... and why do the services get corrupted after restart?
... why isn't a new token obtained automatically?

Any help would be appreciated.

Peter

Re: Why do I get "Provided token does not have permission to subscribe" after restart?

MattFoster — Tue, 19 May 2020 22:46:23 GMT

Morning, for anyone who bumps into this issue, check your stream service is shared correctly. By default when publishing from the stream service it doesn't get shared.
Once I shared to everyone (offline development environment in my case) the errors stopped appearing.

Good luck,

Matt

Re: Why do I get "Provided token does not have permission to subscribe" after restart?

DuongHB — Tue, 06 Jul 2021 02:48:36 GMT

We got same error "Provided token does not have permission to subscribe".

Sharing public to everyone not work.

I found a token is used when wss subscribed.

The service was published using a member account (with admin privilege) . We try to change to publish using initial portal admin account and it works!

Re: Why do I get "Provided token does not have permission to subscribe" after restart?

RoxaneParadis — Wed, 19 Jul 2023 18:53:25 GMT

We encountered the same issue with GeoEvent Server version 11.1, even when publishing the services with the primary administrator account.

After numerous tests, we discovered that moving/creating the stream service in a folder other than 'root' caused the problem. We received the following error in the logs (karaf.log).

Therefore, we moved all the services back to the 'admin/root' folder.

Subsequently, the following error appeared for all our services using the 'store latest' option:

(index):150 [esri.layers.graphics.sources.connections.GeoEventConnection] websocket-connection WebSocket closed unexpectedly with error code 1011.

For these stream services, a restart of GeoEvent Server allowed us to restore everything

Re: Why do I get "Provided token does not have permission to subscribe" after restart?

MaxKirschling — Tue, 21 Jan 2025 17:35:46 GMT

This particular problem was driving us crazy! Moving the streaming services to the root folder on our Portal fixed it!!! Nice catch on a very strange issue.

Re: Why do I get "Provided token does not have permission to subscribe" after restart?

CalvinHarmin — Tue, 21 Jan 2025 17:37:38 GMT

Wow I think that was our problem. I moved a stream service from my Portal root to a subfolder for organization purposes. I didn't putt 2 and 2 together to realize that was the only change I had recently made, and that this had suddenly borked our stream. We were about to start completely tearing down and rebuilding all of our services to try to figure out the problem. You definitely saved us a lot of headache. Did anyone from ESRI ever respond about this issue? I wonder if this is a bug that continues beyond 11.1?