Adam Horacek

Hi @inyutin, thanks for the reply. I think this is somewhere in the middle between aiohttp and retry lib. The reason I proposed this here is because I think it's...

> Hi [@adamko147](https://github.com/adamko147), thanks for the proposal! > > I will bring this issue to team and get relevant folks involved to review the approach described. Thank you @yycptt. Meanwhile...

Hi @yycptt did you have a chance to discuss this issue with team already? Thanks in advance for any update on this.

> LGTM. Could you also open a PR to document this in our documentation repo: https://github.com/temporalio/documentation/blob/main/docs/production-deployment/self-hosted-guide/security.mdx#default-jwt-claimmapper? @bergundy, will do that! Thanks, appreciate the support!

I would have a suggestion, why to decide based on authorization settings? could we simplify it with settings ```yaml server: frontend: enabled: false # other config for frontend component internalFrontend:...

> > Yeah, I like that approach better. I would still need to know when to remove the publicClient stuff, I can probably add another config value for that. I...

> There appears to be another PR to accomplish this here as well: #602 I like the #602, it's kind of the implementation I had in mind. @dleblanc would #602...

Hi @mxk, I've encountered the same scenario and solved by enabling internal-fronted service and deploying own frontend with JWT auth enabled. with internal-fronted, internal temporal components do not need to...

Hi @SAP/jenkins-library-team, do you think I should keep the PR open? Haven't received any feedback in last 2 months. Thank you!