# Authorization, Untrusted workflow creation and namespace authentication

**URL:** <https://community.temporal.io/t/authorization-untrusted-workflow-creation-and-namespace-authentication/632>\
**Category:** Community Support\
**Tags:** auth\
**Created:** [September 15, 2020, 11:05pm UTC](https://community.temporal.io/t/authorization-untrusted-workflow-creation-and-namespace-authentication/632 "2020-09-15T23:05:09Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![SergeyBykov](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/sergeybykov/32/335_2.png) [@SergeyBykov](https://community.temporal.io/u/SergeyBykov)\
**Post date:** [March 26, 2021, 6:30pm UTC](https://community.temporal.io/t/authorization-untrusted-workflow-creation-and-namespace-authentication/632/8 "2021-03-26T18:30:28Z")

</div>

We have a Go sample - [customization-samples/extensibility/authorizer at master · temporalio/customization-samples · GitHub](https://github.com/temporalio/customization-samples/tree/master/extensibility/authorizer) of how one can implement authorization logic. Temporal server by itself does not impose any authorization. It is the job of the pluggable Authorizer and ClaimMapper components. ClaimMapper is responsible for translating identity information of the caller, from the TLS cert and/or JWT token, into a set of role claims that Authorizer uses as input for authorization decisions.

---

_[View the full topic](https://community.temporal.io/t/authorization-untrusted-workflow-creation-and-namespace-authentication/632)._