Updating titles to match summary

This commit is contained in:
Pedro Igor 2016-12-02 13:25:43 -02:00
parent 0a05e599fa
commit 6e3bf914c7
13 changed files with 20 additions and 20 deletions

View file

@ -11,14 +11,14 @@
.. link:topics/getting-started/hello-world/overview.adoc[Securing a Servlet Application]
... link:topics/getting-started/hello-world/create-realm.adoc[Creating a Realm]
... link:topics/getting-started/hello-world/create-realm.adoc[Creating a Realm and a User]
... link:topics/getting-started/hello-world/create-resource-server.adoc[Enabling Authorization Services]
... link:topics/getting-started/hello-world/deploy.adoc[Build, Deploy, and Test]
... link:topics/getting-started/hello-world/deploy.adoc[Build, Deploy, and Test Your Application]
.. link:topics/example/overview.adoc[Examples]
{% endif %}
{% endif %}
. link:topics/resource-server/overview.adoc[Managing Resource Servers]
@ -28,9 +28,9 @@
.. link:topics/resource-server/default-config.adoc[Default Configuration]
.. link:topics/resource-server/import-config.adoc[Exporting and Importing Authorization Configuration]
.. link:topics/resource-server/import-config.adoc[Export and Import Authorization Configuration]
. link:topics/resource/overview.adoc[Managing Resources]
. link:topics/resource/overview.adoc[Managing Resources and Scopes]
.. link:topics/resource/view.adoc[Viewing Resources]
@ -58,11 +58,11 @@
. link:topics/permission/overview.adoc[Managing Permissions]
.. link:topics/permission/create-resource.adoc[Creating Resource-based Permissions]
.. link:topics/permission/create-resource.adoc[Creating Resource-Based Permissions]
... link:topics/permission/typed-resource-permission.adoc[Typed Resource Permissions]
.. link:topics/permission/create-scope.adoc[Creating Scope-based Permissions]
.. link:topics/permission/create-scope.adoc[Creating Scope-Based Permissions]
.. link:topics/permission/decision-strategy.adoc[Policy Decision Strategies]

View file

@ -1,5 +1,5 @@
[[_getting_started_hello_world_deploy]]
=== Building, Deploying, and Testing Your Application
=== Build, Deploy, and Test Your Application
Now that the *hello-world-authz-service* resource server (or client) is properly configured and authorization services are enabled, it can be deployed to the server.

View file

@ -1,5 +1,5 @@
[[_getting_started_hello_world_overview]]
=== Hello World
=== Securing a Servlet Application
The purpose of this getting started guide is to get you up and running as quickly as possible so that you can experiment with and test various authorization features provided by {{book.project.name}}.
This quick tour relies heavily on the default database and server configurations and does not cover complex deployment options.

View file

@ -1,5 +1,5 @@
[[_permission_create_resource]]
=== Creating Resource-based Permissions
=== Creating Resource-Based Permissions
A resource-based permission defines a set of one or more resources to protect using a set of one or more authorization policies.

View file

@ -1,5 +1,5 @@
[[_permission_create_scope]]
=== Creating Scope-based Permissions
=== Creating Scope-Based Permissions
A scope-based permission defines a set of one or more scopes to protect using a set of one or more authorization policies. Unlike resource-based permissions, you can use this permission type to create permissions not only for a resource, but also for the scopes associated with it, providing more granularity when defining the permissions that govern your resources and the actions that can be performed on them.

View file

@ -1,5 +1,5 @@
[[_policy_evaluation_overview]]
== Policy Evaluation Tool
== Evaluating and Testing Policies
When designing your policies, you can simulate authorization requests to test how your policies are being evaluated.

View file

@ -1,5 +1,5 @@
[[_policy_aggregated]]
=== Aggregated Policies
=== Aggregated Policy
As mentioned previously, {{book.project.name}} allows you to build a policy of policies, a concept referred to as policy aggregation. You can use policy aggregation to reuse existing policies to build more complex ones and keep your permissions even more decoupled from the policies that are evaluated during the processing of authorization requests.

View file

@ -1,5 +1,5 @@
[[_policy_evaluation_api]]
=== Evaluation API
=== Policy Evaluation API
When writing rule-based policies using JavaScript or JBoss Drools, {{book.project.name}} provides an Evaluation API that provides useful information to help determine whether a permission should be granted.

View file

@ -1,5 +1,5 @@
[[_resource_server_import_config]]
=== Exporting and Importing Configuration Files
=== Export and Import Authorization Configuration
The configuration settings for a resource server (or client) can be exported and downloaded. You can also import an existing configuration file for a resource server. Importing and exporting a configuration file is helpful when you want to create an initial configuration for a resource server or to update an existing configuration. The configuration file contains definitions for:

View file

@ -1,5 +1,5 @@
[[_service_authorization_aat]]
=== Authorization API Token
=== What is a AAT and How to Obtain It
An authorization API token (AAT) is a special OAuth2 access token with the scope *uma_authorization*. When you create a user, {{book.project.name}} automatically
assigns the role _uma_authorization_ to the user. The _uma_authorization_ role is a default realm role.

View file

@ -1,5 +1,5 @@
[[_service_client_api]]
=== Authorization Client API
=== Authorization Client Java API
If you are using Java, you can access all {{book.project.name}} {{book.project.module}} using a client API.

View file

@ -1,5 +1,5 @@
[[_service_protection_resources_api]]
=== Managing Resources Using the Protection API
=== Managing Resources
Resource servers can manage their resources remotely using a UMA-compliant endpoint.

View file

@ -1,5 +1,5 @@
[[_service_protection_whatis_obtain_pat]]
=== What is a PAT and How to Obtain It?
=== What is a PAT and How to Obtain It
A *protection API token* (PAT) is a special OAuth2 access token with a scope defined as *uma_protection*. When you create a resource server, {{book.project.name}} automatically
creates a role, _uma_protection_, for the corresponding client application and associates it with the client's service account.