Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions assets/main.css
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ body {
color: #fed136; }

p {
font-size: 14px;
font-size: 15px;
line-height: 1.75; }

p.large {
Expand Down Expand Up @@ -37,7 +37,8 @@ h1, h2, h3, h4, h5, h6 {
font-weight: 700; }

.img-centered {
margin: 0 auto; }
margin: 0 auto;
vertical-align: middle; }

.bg-light-gray {
background-color: #eeeeee; }
Expand Down
6 changes: 5 additions & 1 deletion contact.html
Original file line number Diff line number Diff line change
Expand Up @@ -94,13 +94,17 @@ <h3 class="section-heading">GitHub</h3>
<div class="text-left benefits">
<h3 class="section-heading">Slack</h3>
<p>We use Slack for discussion and support. For any Athenz questions, join the <code>`#general`</code> channel on the <a href="https://athenz.slack.com">Athenz Slack team</a>. For everything else, join the <code>`#random`</code> channel.</p>
</div>
</div>
<div class="row">
<div class="text-left benefits">
<h3 class="section-heading">Groups</h3>
<p>You may also use the following discussion groups:
<ul>
<li><a href="https://groups.google.com/forum/#!forum/athenz-dev">Athenz-Dev</a> for development discussions
<li><a href="https://groups.google.com/forum/#!forum/athenz-users">Athenz-Users</a> for users questions
</ul>
</p>

</div>
</div>
<div class="row">
Expand Down
10 changes: 5 additions & 5 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -141,14 +141,14 @@ <h4 class="service-heading">Service-based security profile</h4>
<div class="row">

<h2 class="section-heading text-center">Providing RBAC for your needs</h2>
<p><div class="row text-center">Athenz is a set of services and libraries supporting role-based authorization (RBAC) for provisioning and configuration (centralized authorization) use cases as well as serving/runtime (decentralized authorization) use cases to handle on-box enforcement.</div></p>
<div class="row text-center"><p>Athenz is a set of services and libraries supporting role-based authorization (RBAC) for provisioning and configuration (centralized authorization) use cases as well as serving/runtime (decentralized authorization) use cases to handle on-box enforcement.</p></div>
<div class="row text-center">
<h3 class="service-heading">Centralized Access Control</h3>

</div>
<div class="row">
<div class="col-md-6 text-center" >
<img src="/assets/img/about/CentralizeUseCase.png" width="100%">
<div class="col-md-6 img-centered">
<br><br><img src="/assets/img/about/CentralizeUseCase.png" width="100%"">
</div>
<div class="col-md-6">
<p>A traditional centralized access control model requires any Athenz enabled application to contact Athenz Management Service directly to determine if a specific authenticated principal (user and/or service) has been authorized to carry out the given action on the requested resource. The application receives a simple boolean answer whether or not the request should be processed or rejected. In this model, the Athenz Management Service is the only component that needs to be deployed and managed within your environment. It is suitable for provisioning and configuration use cases where the number of requests processed by the server is small and the latency for authorization checks is not important.</p>
Expand All @@ -163,11 +163,11 @@ <h3 class="service-heading">Decentralized Access Control</h3>
<div class="row" >
<div class="col-md-6" >
<p>For serving/runtime use cases where the application is required to handle large number of requests per second and latency is a concern, Athenz provides a decentralized access control model where the check to see if a given principal (user and/or service) has been authorized to carry out the given action on the requested service is done on the host itself using the Athenz local policy engine library.</p>
<p>With the decentralized model, the authorization policies defining which roles have been authorized to carry out specific actions on resources are asynchronously updated on application hosts and used by the Athenz local policy engine to evaluate the authorization check. In this model, the principal needs to contact Athenz Token Service first to retrieve an Authorization RoleToken for the request and submit that Token as part of its request to the Athenz protected service.</p>
<p>With the decentralized model, the authorization policies defining which roles have been authorized to carry out specific actions on resources are asynchronously updated on application hosts and used by the Athenz local policy engine to evaluate the authorization check. In this model, the principal needs to contact Athenz Token Service first to retrieve an Authorization RoleToken for the request and submit that Token as part of its request to the Athenz protected service.</p>
<p>The diagram on the right shows a typical decentralized authorization request handled by Athenz protected service.</p>
</div>
<div class="col-md-6 text-center" >
<img src="/assets/img/about/DecentralizeUseCase.png" width="100%">
<br><br><br><img src="/assets/img/about/DecentralizeUseCase.png" width="100%">
</div>
</div>
</div>
Expand Down