Externalize authorization in Spring Boot so policy changes don't need a redeploy

Short answer: To externalize authorization in Spring Boot, call the Permit.io Java SDK from your controller and keep the rules in Permit, so a policy change needs no redeploy. Use it when roles and permissions change more often than your releases. Don't use it when a few fixed role checks, such as @PreAuthorize annotations, in one application cover your needs.

Fact	Value
Question this page answers	How do I externalize authorization in Spring Boot so policy changes don't need a redeploy?
Where the check runs	the POST /posts handler in PermitController, which calls permit.check().
SDK	Java SDK, io.permit:permit-sdk-java on Maven Central. This tutorial uses version 2.2.5. See Check permissions with the Java SDK.
PDP	A container PDP at http://localhost:7766 in this tutorial, or the Cloud PDP. See PDP overview.
Models used	RBAC for the Author and Reader roles. ReBAC and ABAC are also supported.
Policy changes	You change roles and permissions in the Permit dashboard. The application code and the deployment stay the same.
Free tier	Community plan, labeled "Free Forever" on the Permit.io pricing page: MAU 1000, Tenants 20, Authorization Queries No Limit, Environments 3, PDP Instances No Limit.
Audit	Each check appears on the Audit Log screen of the Permit dashboard.
Open source	The Edge PDP (permitio/PDP), OPAL, cedar-agent, the Permit SDKs, and the Permit CLI are open source. See Open-source fallback.

Build a Spring Boot REST controller for a blogging platform that registers users in Permit.io and allows only users with the Author role to create posts. This tutorial is for Java backend developers who want to enforce Permit.io policies from Spring Boot endpoints.

When you finish, your Spring Boot app has two endpoints:

Endpoint	What it does
POST /register	Syncs a user to Permit.io and assigns the user the Reader role in the default tenant
POST /posts	Calls permit.check() and returns 403 unless the user in the request body has permission to create a Post

Prerequisites

• A Permit.io account. See Create a Permit.io account.
• A Java development kit and Maven.
• A Spring Boot project with the Spring Web dependency, in the package com.example.permitdemo. You can generate one with Spring Initializr.
• Node.js and npm, to install the Permit CLI.
• Docker, to run the policy decision point (PDP) container.

1. Configure the policy in Permit

Create the blogging platform policy with the Permit CLI. If your environment already has a policy with a Post resource and an Author role that can create posts, skip to 2. Get your API key.

1

Install the Permit CLI

The Permit CLI creates policies and runs the PDP from your terminal. Install the CLI with npm:

npm install -g @permitio/cli

Run permit to confirm that the CLI is installed.

2

Sign in with the Permit CLI

Authenticate the CLI with your Permit.io account:

permit login

The command opens a browser window where you sign in. After you sign in, the CLI uses your default environment. To use a different environment, run permit env select and choose the environment.

3

Apply the blogging platform template

Permit CLI templates create a policy with predefined resources, roles, and rules. To see the available templates, run permit env template list. The template source files are in the Permit CLI repository.

Apply the blogging-platform template to your environment:

permit env template apply --template blogging-platform

The CLI prints a success message when the template is applied.

4

Review the policy in the Policy Editor

In the Permit dashboard, select your project and open the Policy screen.

The blogging-platform template creates:

Policy element	What the template defines
Resources	Post (with a premium boolean attribute) and Comment, each with create, read, update, and delete actions
Roles	Admin (all actions), Author (create and read posts, read comments), Reader (create and read comments), and Premium Reader (read posts and comments)
Relationship	A Post is the parent of its Comment instances. An Author of a post instance becomes a Moderator of the comments on that post. This rule is relationship-based access control (ReBAC).
Resource set	Free Post contains posts where premium is false. Readers can read free posts. This rule is attribute-based access control (ABAC).

This tutorial uses one rule from the policy: the Author role can create a Post, and the Reader role cannot. To change which role can perform an action, check or clear the box in the Policy Editor.

2. Get your API key

Your Spring Boot app and the PDP authenticate with Permit.io with your environment API key. Copy the API key of the environment where you applied the template. See Get your API key.

Keep the API key out of your code

Anyone with the environment API key can change that environment's policy through the Permit API. Load the key from an environment variable, and don't commit it.

3. Run the PDP

The PDP evaluates each permission check against your policy. Start a PDP container with the Permit CLI:

permit pdp run

The command starts the PDP in Docker and prints the container ID and name. The PDP listens on port 7766, so your app connects to it at http://localhost:7766.

The Free Post resource set is an ABAC rule, and the Cloud PDP doesn't evaluate ABAC rules, so run the container PDP for this policy. To run the container with docker run instead, or to check that the PDP is healthy, see Run the PDP.

4. Build the Spring Boot app

1

Install the Java SDK

Add the Permit Java SDK dependency to your pom.xml file:

<dependency>
  <groupId>io.permit</groupId>
  <artifactId>permit-sdk-java</artifactId>
  <version>2.2.5</version>
</dependency>

Run mvn clean install to download the dependency. The Java SDK is published to Maven Central as io.permit:permit-sdk-java. To use a later release, change the version value. For all SDK options, see Check permissions with the Java SDK.

2

Check the application class

Your main application class starts Spring Boot. A project generated with Spring Initializr already has a class like this one:

package com.example.permitdemo;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class PermitdemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(PermitdemoApplication.class, args);
    }
}

3

Create the Permit controller

Create a PermitController class in the same package:

package com.example.permitdemo;

import io.permit.sdk.Permit;
import io.permit.sdk.PermitConfig;
import io.permit.sdk.api.PermitApiError;
import io.permit.sdk.api.PermitContextError;
import io.permit.sdk.enforcement.Resource;
import io.permit.sdk.enforcement.User;
import io.permit.sdk.openapi.models.UserRead;
import io.permit.sdk.openapi.models.UserCreate;
import io.permit.sdk.openapi.models.RoleAssignmentRead;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.*;

import java.io.IOException;
import java.util.Map;

@RestController
public class PermitController {

    private final Permit permit;

    public PermitController(
            @Value("${PERMIT_API_KEY}") String apiKey,
            @Value("${PDP_URL:http://localhost:7766}") String pdpUrl
    ) {
        this.permit = new Permit(
                new PermitConfig.Builder(apiKey)
                        .withPdpAddress(pdpUrl)
                        .withDebugMode(true)
                        .build()
        );
    }    
}

The constructor creates a Permit client from two properties that Spring resolves from environment variables:

Variable	Value
PERMIT_API_KEY	Your environment API key from 2. Get your API key. The app fails to start when this variable is missing.
PDP_URL	The PDP address from 3. Run the PDP. The controller uses http://localhost:7766 when this variable is missing.

4

Add the /register and /posts endpoints

Add the following methods inside the PermitController class, before the closing brace:

    // Register a user and assign the Reader role
    @PostMapping("/register")
    public ResponseEntity<?> register(@RequestBody Map<String, String> body) {
        String email = body.get("email");
        String firstName = body.get("first_name");
        String lastName = body.get("last_name");

        if (email == null || firstName == null || lastName == null) {
            return ResponseEntity.badRequest().body(Map.of("error", "Missing required fields"));
        }

        try {
            UserRead user = permit.api.users.sync(
                    new UserCreate(email)
                            .withEmail(email)
                            .withFirstName(firstName)
                            .withLastName(lastName)
            ).getResult();
            // Assign a role to the user ("Reader" in tenant "default")
            RoleAssignmentRead roleAssignment = permit.api.users.assignRole(email, "Reader", "default");
            return ResponseEntity.status(HttpStatus.CREATED).body(Map.of(
                "message", "User registered and role assigned",
                "user", user,
                "role_assignment", roleAssignment
            ));
        } catch (IOException | PermitApiError | PermitContextError e) {
            e.printStackTrace();
            return ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR)
                    .body(Map.of("error", "Failed to sync user or assign role"));
        }
    }

    // Check if the user has access to create a post
    @PostMapping("/posts")
    public ResponseEntity<?> posts(@RequestBody Map<String, Object> body) {
        String userKey = (String) body.get("user");
        String action = "create";
        String resource = "Post";

        if (userKey == null) {
            return ResponseEntity.badRequest().body(Map.of("error", "Missing required fields"));
        }

        try {
            User user = new User.Builder(userKey).build();
            Resource res = new Resource.Builder(resource).build();
            boolean permitted = permit.check(user, action, res);
            if (permitted) {
                return ResponseEntity.ok(Map.of("message", "User is permitted"));
            } else {
                return ResponseEntity.status(HttpStatus.FORBIDDEN).body(Map.of("message", "User is not permitted"));
            }
        } catch (Exception e) {
            e.printStackTrace();
            return ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR)
                    .body(Map.of("error", "Permission check failed"));
        }
    }

The controller has two endpoints:

Endpoint	What it does
POST /register	Syncs the user to Permit.io with permit.api.users.sync(), with the email address as the user key, then assigns the Reader role in the default tenant with permit.api.users.assignRole(). Returns 201 with the user and the role assignment.
POST /posts	Asks the PDP whether the user key in the user field of the request body can create a Post. Returns "User is permitted", or 403 with "User is not permitted".

Both endpoints return 400 when a required field is missing and 500 when a call to Permit.io or the PDP fails. To protect other endpoints, such as commenting or editing, change the action and resource values.

note

In a production app, take the user key from your authenticated session. This example reads the user key from the request body so that you can test the endpoint with curl.

5

Start the Spring Boot app

Set the environment variables and start the app, replacing <YOUR_API_KEY> with your API key:

export PERMIT_API_KEY=<YOUR_API_KEY>
export PDP_URL=http://localhost:7766
mvn spring-boot:run

The app listens on http://localhost:8080, the Spring Boot default port.

5. Test the permission check

Register two users, give one of them the Author role, and confirm that the PDP allows only that user to create a post.

1

Register two users

In a second terminal, register John and Emma:

curl -X POST http://localhost:8080/register \
  -H "Content-Type: application/json" \
  -d '{"email": "john@example.com", "first_name": "John", "last_name": "Doe"}'

curl -X POST http://localhost:8080/register \
  -H "Content-Type: application/json" \
  -d '{"email": "emma@example.com", "first_name": "Emma", "last_name": "Den"}'

Each request returns HTTP 201 with "message": "User registered and role assigned", the synced user under user, and the Reader role assignment under role_assignment.

2

Assign John the Author role

Both users have the Reader role, which can't create posts. Give John the Author role in the Permit dashboard:

1. Open the Directory screen and select john@example.com to open the Edit User panel.
2. Under Permissions Per Tenant, select the Default Tenant.
3. In Top Level Access, add the Author role.
4. Click Save.

For other ways to assign roles, including the API and SDK, see Sync users.

3

Check that John can create a post and Emma can't

Send a POST /posts request for John:

curl -X POST http://localhost:8080/posts \
  -H "Content-Type: application/json" \
  -d '{"user": "john@example.com"}'

The PDP allows the request because John has the Author role. The app returns {"message":"User is permitted"}.

Send the same request for Emma:

curl -X POST http://localhost:8080/posts \
  -H "Content-Type: application/json" \
  -d '{"user": "emma@example.com"}'

The PDP denies the request because Emma has only the Reader role. The app returns HTTP 403 with {"message":"User is not permitted"}.

Each check also appears in the Audit Log screen of the Permit dashboard, with the user, action, resource, and decision.

6. Change the policy without redeploying

Your Spring Boot code contains the enforcement point: the POST /posts handler in PermitController, which calls permit.check(). The rule about which role may create a post is policy in Permit, not code in your app. Change the rule and watch the app respond without restarting the Spring Boot app.

1. Keep the app and the PDP running, with John's Author role from 5. Test the permission check.
2. In the Permit dashboard, open the Policy screen. Clear the box for the create action on Post in the Author role column.
3. Send John's POST /posts request from step 5 again. The PDP denies it, and the app returns the same 403 response that Emma received.
4. Check the box again and send the request once more. The app returns the successful response again.

Updates reach a PDP in the background, so repeat the request if you still see the previous result. The change doesn't appear in a pull request or a build, because it is a policy change and not a code change. To review policy changes like code, see GitOps.

Frequently asked questions

How do I externalize authorization in Spring Boot so policy changes don't need a redeploy?

Keep the enforcement point in your code and move the rules to Permit. Your handler asks the PDP whether a user can perform an action on a resource, using the Java SDK, and the PDP answers from the policy you edit in the Permit dashboard. Section 6 changes a rule and sends the same request again, with no code change.

Does a role or permission change require restarting the Spring Boot app?

No. Roles, permissions, and role assignments live in Permit. The PDP receives updates in the background, so the next check uses the updated policy.

Where does the authorization decision run?

In the PDP, a separate service that your app calls over the network. This tutorial runs the PDP as a container at http://localhost:7766. The Cloud PDP is a managed alternative that supports RBAC and ReBAC. See Cloud PDP capabilities.

When should I keep authorization in Spring Boot code instead?

When a small set of fixed roles lives in one application and changes only with a code release, checks in the application are enough. Use Permit.io when roles change more often than releases, several services share the rules, or non-developers manage access.

Which Permit SDK does this tutorial use?

Java SDK, io.permit:permit-sdk-java on Maven Central. This tutorial uses version 2.2.5. See Check permissions with the Java SDK.

What does the free tier include?

The Community plan on the Permit.io pricing page lists MAU 1000, Tenants 20, Authorization Queries No Limit, and PDP Instances No Limit.

Next steps

• Check permissions with the Java SDK: SDK installation, configuration, and more permit.check() examples.
• Check permissions with permit.check(): check against tenants, resource instances, and attributes.
• Build RBAC policies: create roles and permissions for your own resources.
• Deploy the PDP to production: run the PDP next to your services.

Next step

Going to production? Review the PDP deployment checklist, or talk to an engineer about scale and latency.