# Workflow for OIDC login on Linux

**URL:** https://openziti.discourse.group/t/workflow-for-oidc-login-on-linux/4848
**Category:** Ziti Edge Tunnel
**Created:** [July 7, 2025, 3:39pm UTC](https://openziti.discourse.group/t/workflow-for-oidc-login-on-linux/4848 "2025-07-07T15:39:29Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![SBDJ](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@SBDJ](https://openziti.discourse.group/u/SBDJ)
#### Post date: [July 7, 2025, 3:39pm UTC](https://openziti.discourse.group/t/workflow-for-oidc-login-on-linux/4848/1 "2025-07-07T15:39:29Z")

</div>

Hi,

Apologies for another OIDC related topic; my testing on Windows and Mac has been going well, but now I'm trying to test on Linux with less success.

Is there a link to working with the edge tunneller on Linux and OIDC? I've not been having much luck so far.

I've tried enrolling the network JWT, but I get a message the ziti context is disabled. I've also tried the add function, which doesn't complain about the context - it says it was successful. I then try logging in with ext-jwt-login but get a "ziti context not found".

ziti-edge-tunnel dump gives a success but no data. The logs show the identity being loaded, and the external auth configuration. I see ext auth: login\_with\_ext\_signer, and the identity being updated to action 'needs\_ext\_login'.

I'm hoping there is some documentation I've overlooked, like last time!

---

<div class="post-metadata">

### Author: ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)
#### Post date: [July 7, 2025, 3:41pm UTC](https://openziti.discourse.group/t/workflow-for-oidc-login-on-linux/4848/2 "2025-07-07T15:41:56Z")

</div>

Read through this thread. There's a bug that makes using it more difficult than it needs to be on linux at this time.I think if you read that thread you'll find what you need.

> [@Linux ext-jwt-signer w/Google OIDC](https://openziti.discourse.group/t/linux-ext-jwt-signer-w-google-oidc/4798/11):
>
> I'm up and running now with my OIDC identity now. To answer my own question. The green dot by my identity wasn't lit, because my Identity didn't have a router policy that allowed me to connect to the edge router that was running my services. As soon as I added that the green dot came back on. That's router connection status, not ziti service connection status. I created services for nfsd, portmapper, and mountd, and then voila I can mount nfs through my ziti host. Whooo hoo! I still think the…

---

<div class="post-metadata">

### Author: ![SBDJ](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@SBDJ](https://openziti.discourse.group/u/SBDJ)
#### Post date: [July 7, 2025, 3:57pm UTC](https://openziti.discourse.group/t/workflow-for-oidc-login-on-linux/4848/3 "2025-07-07T15:57:55Z")

</div>

That works, thanks.

For anyone else who might find this in the future:

```auto
ziti-edge-tunnel add --jwt "$(< .network.jwt)" --identity myidentity
ziti-edge-tunnel ext-jwt-login --identity /opt/openziti/etc/myidentity.json --provider "Name of JWT Signer"

```

Some notes:

For ext-jwt-login, the identity path has to be absolute. I also had to pass the name of the External JWT Signer as the provider.

This then returns a URL which you can use to authenticate - and you'll have to fix the escaped slashes at the start first too.

But it works 🙂
