{"id":3957,"date":"2025-12-24T10:00:00","date_gmt":"2025-12-24T15:00:00","guid":{"rendered":"https:\/\/www.mymiller.name\/wordpress\/?p=3957"},"modified":"2025-12-18T13:05:24","modified_gmt":"2025-12-18T18:05:24","slug":"mastering-spring-authorization-server-architectural-guide","status":"publish","type":"post","link":"https:\/\/www.mymiller.name\/wordpress\/spring-admin\/mastering-spring-authorization-server-architectural-guide\/","title":{"rendered":"Mastering Spring Authorization Server: Architectural Guide"},"content":{"rendered":"\n

As a Software Architect, transitioning from the legacy spring-security-oauth2<\/code> to the modern Spring Authorization Server (SAS)<\/strong> is a critical shift. This guide provides a deep dive into building a robust identity platform integrated with Spring Cloud Gateway<\/strong> and Social Logins<\/strong>.<\/p>\n\n\n\n

1. Core Architecture: How it Works<\/h2>\n\n\n\n

Spring Authorization Server is the official successor to the legacy OAuth stack. It is built as a standalone library (not a separate product like Keycloak) that you embed in a Spring Boot application.<\/p>\n\n\n\n

The OAuth 2.1 \/ OIDC 1.0 Flow<\/h3>\n\n\n\n
    \n
  1. Client Authentication<\/strong>: The client (e.g., Spring Cloud Gateway) redirects the user to the SAS \/oauth2\/authorize<\/code> endpoint.<\/li>\n\n\n\n
  2. User Authentication<\/strong>: SAS authenticates the user (via Form Login or Federated Social Login).<\/li>\n\n\n\n
  3. Consent<\/strong>: The user grants permission to the client.<\/li>\n\n\n\n
  4. Token Issuance<\/strong>: SAS issues a JWT<\/strong> (Access Token) and an optional Refresh Token<\/strong>.<\/li>\n<\/ol>\n\n\n\n

    2. Setting Up the Authorization Server (Gradle)<\/h2>\n\n\n\n

    In your build.gradle<\/code>, include the specialized starter:<\/p>\n\n\n\n

    dependencies {\n    implementation 'org.springframework.boot:spring-boot-starter-oauth2-authorization-server'\n    implementation 'org.springframework.boot:spring-boot-starter-oauth2-client' \/\/ For Social Login\n    implementation 'org.springframework.boot:spring-boot-starter-web'\n}\n<\/code><\/pre>\n\n\n\n
    The Configuration Bean<\/h3>\n\n\n\n
    SAS requires several beans to define its behavior. The most important is the RegisteredClientRepository<\/code>.<\/p>\n\n\n\n
    @Configuration\npublic class AuthorizationServerConfig {\n\n    @Bean\n    @Order(1)\n    public SecurityFilterChain authServerSecurityFilterChain(HttpSecurity http) throws Exception {\n        OAuth2AuthorizationServerConfiguration.applyDefaultSecurity(http);\n        http.getConfigurer(OAuth2AuthorizationServerConfigurer.class)\n            .oidc(Customizer.withDefaults());\t\/\/ Enable OpenID Connect 1.0\n        \n        http.exceptionHandling((exceptions) -> exceptions\n            .defaultAuthenticationEntryPointFor(\n                new LoginUrlAuthenticationEntryPoint(\"\/login\"),\n                new MediaTypeRequestMatcher(MediaType.TEXT_HTML)\n            )\n        );\n        return http.build();\n    }\n\n    @Bean\n    public RegisteredClientRepository registeredClientRepository() {\n        RegisteredClient gatewayClient = RegisteredClient.withId(UUID.randomUUID().toString())\n                .clientId(\"gateway-client\")\n                .clientSecret(\"{noop}secret\") \n                .clientAuthenticationMethod(ClientAuthenticationMethod.CLIENT_SECRET_BASIC)\n                .authorizationGrantType(AuthorizationGrantType.AUTHORIZATION_CODE)\n                .authorizationGrantType(AuthorizationGrantType.REFRESH_TOKEN)\n                .redirectUri(\"[http:\/\/127.0.0.1:8080\/login\/oauth2\/code\/gateway](http:\/\/127.0.0.1:8080\/login\/oauth2\/code\/gateway)\")\n                .scope(OidcScopes.OPENID)\n                .scope(OidcScopes.PROFILE)\n                .scope(\"resource.read\")\n                .build();\n\n        return new InMemoryRegisteredClientRepository(gatewayClient);\n    }\n}\n<\/code><\/pre>\n\n\n\n
    3. Role Integration & JWT Customization<\/h2>\n\n\n\n
    In an OAuth2 ecosystem, roles are typically passed as “claims” inside the JWT. By default, SAS doesn’t include user roles in the access token. You must customize the OAuth2TokenCustomizer<\/code>.<\/p>\n\n\n\n
    Customizing the JWT on the Auth Server<\/h3>\n\n\n\n
    This logic runs on the Authorization Server<\/strong> to fetch roles from your UserDetailsService<\/code> and inject them into the token.<\/p>\n\n\n\n
    @Bean\npublic OAuth2TokenCustomizer<JwtEncodingContext> tokenCustomizer() {\n    return (context) -> {\n        if (OAuth2TokenType.ACCESS_TOKEN.equals(context.getTokenType())) {\n            Authentication principal = context.getPrincipal();\n            Set<String> authorities = principal.getAuthorities().stream()\n                    .map(GrantedAuthority::getAuthority)\n                    .collect(Collectors.toSet());\n            \n            \/\/ Add custom \"roles\" claim to the JWT\n            context.getClaims().claim(\"roles\", authorities);\n        }\n    };\n}\n<\/code><\/pre>\n\n\n\n
    Mapping Roles on the Resource Server (Microservices)<\/h3>\n\n\n\n
    Microservices need to know that the roles<\/code> claim in the JWT should be treated as Spring Security authorities (prefixed with ROLE_<\/code>).<\/p>\n\n\n\n
    @Configuration\n@EnableMethodSecurity \/\/ Enables @PreAuthorize\npublic class ResourceServerConfig {\n\n    @Bean\n    public JwtAuthenticationConverter jwtAuthenticationConverter() {\n        JwtGrantedAuthoritiesConverter grantedAuthoritiesConverter = new JwtGrantedAuthoritiesConverter();\n        grantedAuthoritiesConverter.setAuthorityPrefix(\"ROLE_\"); \/\/ Convert 'ADMIN' to 'ROLE_ADMIN'\n        grantedAuthoritiesConverter.setAuthoritiesClaimName(\"roles\"); \/\/ Look for 'roles' claim\n\n        JwtAuthenticationConverter jwtAuthenticationConverter = new JwtAuthenticationConverter();\n        jwtAuthenticationConverter.setJwtGrantedAuthoritiesConverter(grantedAuthoritiesConverter);\n        return jwtAuthenticationConverter;\n    }\n\n    @Bean\n    public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {\n        http\n            .authorizeHttpRequests(auth -> auth.anyRequest().authenticated())\n            .oauth2ResourceServer(oauth2 -> oauth2\n                .jwt(jwt -> jwt.jwtAuthenticationConverter(jwtAuthenticationConverter()))\n            );\n        return http.build();\n    }\n}\n<\/code><\/pre>\n\n\n\n
    4. Social Login & Federated Identity<\/h2>\n\n\n\n
    To allow users to login via Google or GitHub, SAS acts as an OAuth2 Client<\/strong> to those providers while remaining the Authorization Server<\/strong> for your internal microservices.<\/p>\n\n\n\n
    Configuration (application.yml<\/code>)<\/h3>\n\n\n\n
    spring:\n  security:\n    oauth2:\n      client:\n        registration:\n          google:\n            client-id: ${GOOGLE_CLIENT_ID}\n            client-secret: ${GOOGLE_CLIENT_SECRET}\n            scope: openid, profile, email\n<\/code><\/pre>\n\n\n\n
    Enabling Federated Login<\/h3>\n\n\n\n
    In your “Default” Security Filter Chain, swap formLogin()<\/code> for oauth2Login()<\/code>:<\/p>\n\n\n\n
    @Bean\n@Order(2)\npublic SecurityFilterChain defaultSecurityFilterChain(HttpSecurity http) throws Exception {\n    http\n        .authorizeHttpRequests((authorize) -> authorize\n            .anyRequest().authenticated()\n        )\n        .oauth2Login(Customizer.withDefaults()); \n    \n    return http.build();\n}\n<\/code><\/pre>\n\n\n\n
    5. Integration with Spring Cloud Gateway<\/h2>\n\n\n\n
    The Gateway<\/strong> should act as the OAuth2 Client<\/strong>. It handles the login flow and then relays the JWT to downstream microservices.<\/p>\n\n\n\n
    Gateway Dependencies (build.gradle<\/code>)<\/h3>\n\n\n\n
    dependencies {\n    implementation 'org.springframework.cloud:spring-cloud-starter-gateway'\n    implementation 'org.springframework.boot:spring-boot-starter-oauth2-client'\n}\n<\/code><\/pre>\n\n\n\n
    Token Relay Pattern<\/h3>\n\n\n\n
    The TokenRelay<\/code> filter automatically extracts the Access Token from the session and adds it as a Authorization: Bearer <token><\/code> header to downstream requests.<\/p>\n\n\n\n
    spring:\n  cloud:\n    gateway:\n      routes:\n        - id: user-service\n          uri: lb:\/\/user-service\n          predicates:\n            - Path=\/api\/users\/**\n          filters:\n            - TokenRelay= \n  \n  security:\n    oauth2:\n      client:\n        provider:\n          spring-auth-server:\n            issuer-uri: http:\/\/auth-server:9000\n        registration:\n          gateway:\n            provider: spring-auth-server\n            client-id: gateway-client\n            client-secret: secret\n            authorization-grant-type: authorization_code\n            scope: openid, profile, resource.read\n<\/code><\/pre>\n\n\n\n
    6. Securing Spring Boot Admin Server<\/h2>\n\n\n\n
    Securing the Admin Server involves protecting its UI and its communication with client instances.<\/p>\n\n\n\n
    Admin Server as OAuth2 Client (build.gradle<\/code>)<\/h3>\n\n\n\n
    dependencies {\n    implementation 'de.codecentric:spring-boot-admin-server'\n    implementation 'de.codecentric:spring-boot-admin-server-ui'\n    implementation 'org.springframework.boot:spring-boot-starter-oauth2-client'\n}\n<\/code><\/pre>\n\n\n\n
    Security Filter Chain<\/h3>\n\n\n\n
    @Configuration\npublic class AdminSecurityConfig {\n    private final AdminServerProperties adminServer;\n\n    public AdminSecurityConfig(AdminServerProperties adminServer) {\n        this.adminServer = adminServer;\n    }\n\n    @Bean\n    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {\n        SavedRequestAwareAuthenticationSuccessHandler successHandler = \n            new SavedRequestAwareAuthenticationSuccessHandler();\n        successHandler.setTargetUrlParameter(\"redirectTo\");\n        successHandler.setDefaultTargetUrl(this.adminServer.getContextPath() + \"\/\");\n\n        http.authorizeHttpRequests(authorize -> authorize\n                .requestMatchers(this.adminServer.getContextPath() + \"\/assets\/**\").permitAll()\n                .requestMatchers(this.adminServer.getContextPath() + \"\/login\").permitAll()\n                .anyRequest().authenticated()\n            )\n            .oauth2Login(oauth2 -> oauth2\n                .loginPage(this.adminServer.getContextPath() + \"\/login\")\n                .successHandler(successHandler)\n            )\n            .csrf(csrf -> csrf.disable());\n        \n        return http.build();\n    }\n}\n<\/code><\/pre>\n\n\n\n
    7. Securing Downstream Microservices (Resource Servers)<\/h2>\n\n\n\n
    Microservices behind the gateway only need to trust the Spring Authorization Server<\/strong>.<\/p>\n\n\n\n
    Security Configuration with Method Security<\/h3>\n\n\n\n
    @RestController\n@RequestMapping(\"\/api\/orders\")\npublic class OrderController {\n\n    @GetMapping(\"\/{id}\")\n    @PreAuthorize(\"hasRole('USER')\") \/\/ Role-based security at the method level\n    public Order getOrder(@PathVariable String id) {\n        return orderService.findById(id);\n    }\n\n    @DeleteMapping(\"\/{id}\")\n    @PreAuthorize(\"hasRole('ADMIN')\")\n    public void deleteOrder(@PathVariable String id) {\n        orderService.delete(id);\n    }\n}\n<\/code><\/pre>\n\n\n\n
    Summary for Architects<\/h2>\n\n\n\n
    Component<\/strong><\/td>Role<\/strong><\/td>Role Management<\/strong><\/td><\/tr>
    Auth Server<\/strong><\/td>IDP<\/td>Fetches roles from DB and embeds them in JWT via OAuth2TokenCustomizer<\/code>.<\/td><\/tr>
    Gateway<\/strong><\/td>Client<\/td>Agnostic of internal roles; simply relays the token.<\/td><\/tr>
    Resource Server<\/strong><\/td>API<\/td>Converts JWT roles<\/code> claim to GrantedAuthorities<\/code> and enforces via @PreAuthorize<\/code>.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    By centralizing role mapping in the OAuth2TokenCustomizer<\/code>, you ensure that all microservices receive a consistent security context regardless of the authentication source (Social vs. Form Login).<\/p>\n","protected":false},"excerpt":{"rendered":"
    As a Software Architect, transitioning from the legacy spring-security-oauth2 to the modern Spring Authorization Server (SAS) is a critical shift. This guide provides a deep dive into building a robust identity platform integrated with Spring Cloud Gateway and Social Logins. 1. Core Architecture: How it Works Spring Authorization Server is the official successor to the […]<\/p>\n","protected":false},"author":1,"featured_media":3958,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[489],"tags":[69,477,319,490],"series":[],"class_list":["post-3957","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-spring-admin","tag-java-2","tag-oauth","tag-spring","tag-spring-admin"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/12\/Gemini_Generated_Image_dj5ssndj5ssndj5s.avif","jetpack-related-posts":[{"id":3922,"url":"https:\/\/www.mymiller.name\/wordpress\/spng_security\/beyond-rbac-spring-security-6-oauth-2-1-and-the-zero-trust-evolution\/","url_meta":{"origin":3957,"position":0},"title":"Beyond RBAC: Spring Security 6, OAuth 2.1, and the Zero-Trust Evolution","author":"Jeffery Miller","date":"April 20, 2026","format":false,"excerpt":"The journey to Zero Trust (ZT) is an ongoing architectural evolution, not a single deployment. While the foundational principles\u2014never trust, always verify\u2014are clear, implementing them in a distributed microservice environment requires rigorous adherence to modern standards. For Spring architects and developers, Spring Security 6 and the Spring Authorization Server provide\u2026","rel":"","context":"In "Spring Security"","block_context":{"text":"Spring Security","link":"https:\/\/www.mymiller.name\/wordpress\/category\/spng_security\/"},"img":{"alt_text":"","src":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/11\/coding-1841550_1280.avif","width":350,"height":200,"srcset":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/11\/coding-1841550_1280.avif 1x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/11\/coding-1841550_1280.avif 1.5x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/11\/coding-1841550_1280.avif 2x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/11\/coding-1841550_1280.avif 3x"},"classes":[]},{"id":3438,"url":"https:\/\/www.mymiller.name\/wordpress\/spring\/architecting-with-spring-and-spring-cloud\/","url_meta":{"origin":3957,"position":1},"title":"Architecting with Spring and Spring Cloud","author":"Jeffery Miller","date":"December 24, 2025","format":false,"excerpt":"Building a Multi-Service Architecture with Spring 3.1.x and Spring Cloud: Unlocking the Power of Microservices In the ever-evolving landscape of software development, microservices have emerged as a powerful architectural paradigm, enabling organizations to build scalable, resilient, and agile applications. Spring, a widely adopted Java framework, provides a comprehensive suite of\u2026","rel":"","context":"In "Spring"","block_context":{"text":"Spring","link":"https:\/\/www.mymiller.name\/wordpress\/category\/spring\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2023\/11\/field-5236879_640.jpg?fit=640%2C360&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2023\/11\/field-5236879_640.jpg?fit=640%2C360&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2023\/11\/field-5236879_640.jpg?fit=640%2C360&ssl=1&resize=525%2C300 1.5x"},"classes":[]},{"id":3828,"url":"https:\/\/www.mymiller.name\/wordpress\/spring-gateway\/load-balancing-your-microservices-configuring-spring-cloud-gateway-with-spring-discovery-server\/","url_meta":{"origin":3957,"position":2},"title":"Load Balancing Your Microservices: Configuring Spring Cloud Gateway with Spring Discovery Server","author":"Jeffery Miller","date":"December 24, 2025","format":false,"excerpt":"In a microservices architecture, ensuring high availability and distributing traffic evenly across multiple instances of a service is paramount. Spring Cloud Gateway, when integrated with a Spring Discovery Server (like Netflix Eureka, Consul, or Spring Cloud Service Registry), provides a powerful and straightforward way to achieve client-side load balancing without\u2026","rel":"","context":"In "Spring Gateway"","block_context":{"text":"Spring Gateway","link":"https:\/\/www.mymiller.name\/wordpress\/category\/spring-gateway\/"},"img":{"alt_text":"","src":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/04\/meditation-3814069_1280.avif","width":350,"height":200,"srcset":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/04\/meditation-3814069_1280.avif 1x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/04\/meditation-3814069_1280.avif 1.5x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/04\/meditation-3814069_1280.avif 2x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2025\/04\/meditation-3814069_1280.avif 3x"},"classes":[]},{"id":3632,"url":"https:\/\/www.mymiller.name\/wordpress\/spring_sockets\/real-time-communication-with-spring-boot-websockets-a-comprehensive-guide\/","url_meta":{"origin":3957,"position":3},"title":"Real-Time Communication with Spring Boot WebSockets: A Comprehensive Guide","author":"Jeffery Miller","date":"April 20, 2026","format":false,"excerpt":"In the world of modern web applications, real-time communication has become a necessity. Whether it\u2019s live chat, collaborative editing, or real-time data updates, WebSockets have emerged as the go-to technology to enable seamless, bidirectional communication between the browser and server. In this article, we\u2019ll dive into how to harness the\u2026","rel":"","context":"In "Spring Sockets"","block_context":{"text":"Spring Sockets","link":"https:\/\/www.mymiller.name\/wordpress\/category\/spring_sockets\/"},"img":{"alt_text":"","src":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/07\/cpu-4393380_1280-jpg.avif","width":350,"height":200,"srcset":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/07\/cpu-4393380_1280-jpg.avif 1x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/07\/cpu-4393380_1280-jpg.avif 1.5x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/07\/cpu-4393380_1280-jpg.avif 2x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/07\/cpu-4393380_1280-jpg.avif 3x"},"classes":[]},{"id":3641,"url":"https:\/\/www.mymiller.name\/wordpress\/spng_security\/integrating-java-spring-with-keycloak-a-comprehensive-guide\/","url_meta":{"origin":3957,"position":4},"title":"Integrating Java Spring with Keycloak: A Comprehensive Guide","author":"Jeffery Miller","date":"December 24, 2025","format":false,"excerpt":"Java Spring, a popular framework for building enterprise-level applications, can seamlessly integrate with Keycloak, a robust open-source Identity and Access Management (IAM) solution. This combination offers a powerful way to implement secure authentication, authorization, and user management features in your Spring-based applications. Let\u2019s explore how to achieve this integration along\u2026","rel":"","context":"In "Spring Security"","block_context":{"text":"Spring Security","link":"https:\/\/www.mymiller.name\/wordpress\/category\/spng_security\/"},"img":{"alt_text":"","src":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/08\/ghost-7571881_1280-jpg.avif","width":350,"height":200,"srcset":"https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/08\/ghost-7571881_1280-jpg.avif 1x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/08\/ghost-7571881_1280-jpg.avif 1.5x, https:\/\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/08\/ghost-7571881_1280-jpg.avif 2x"},"classes":[]},{"id":3542,"url":"https:\/\/www.mymiller.name\/wordpress\/spring_open_feign\/simplified-rest-clients-with-openfeign-in-java\/","url_meta":{"origin":3957,"position":5},"title":"Simplified REST Clients with OpenFeign in Java","author":"Jeffery Miller","date":"April 20, 2026","format":false,"excerpt":"OpenFeign, a declarative HTTP client, simplifies REST API interactions in Java. Let\u2019s see how: Dependency: Add OpenFeign to your project (Maven example):  org.springframework.cloud<\/groupId> spring-cloud-starter-openfeign<\/artifactId> <\/dependency> Interface: Define an interface mirroring your REST endpoints: @FeignClient(name = \"myService\", url = \"${myService.url}\") public interface MyServiceClient { @GetMapping(\"\/users\/{id}\") User getUserById(@PathVariable(\"id\") Long id, @RequestHeader(\"Authorization\")\u2026","rel":"","context":"In "Spring Open Feign"","block_context":{"text":"Spring Open Feign","link":"https:\/\/www.mymiller.name\/wordpress\/category\/spring_open_feign\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/06\/technology-7173626_1280.jpg?fit=1200%2C675&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/06\/technology-7173626_1280.jpg?fit=1200%2C675&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/06\/technology-7173626_1280.jpg?fit=1200%2C675&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/06\/technology-7173626_1280.jpg?fit=1200%2C675&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/www.mymiller.name\/wordpress\/wp-content\/uploads\/2024\/06\/technology-7173626_1280.jpg?fit=1200%2C675&ssl=1&resize=1050%2C600 3x"},"classes":[]}],"jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/posts\/3957","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/comments?post=3957"}],"version-history":[{"count":1,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/posts\/3957\/revisions"}],"predecessor-version":[{"id":3959,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/posts\/3957\/revisions\/3959"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/media\/3958"}],"wp:attachment":[{"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/media?parent=3957"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/categories?post=3957"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/tags?post=3957"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.mymiller.name\/wordpress\/wp-json\/wp\/v2\/series?post=3957"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}