You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2022/07/14 00:25:43 UTC

[GitHub] [nifi] exceptionfactory commented on a diff in pull request #6196: NIFI-10217 Refactor Registry Spring Security Configuration

exceptionfactory commented on code in PR #6196:
URL: https://github.com/apache/nifi/pull/6196#discussion_r920610907


##########
nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/NiFiRegistrySecurityConfig.java:
##########
@@ -101,26 +99,17 @@ protected void configure(HttpSecurity http) throws Exception {
                     .anyRequest().fullyAuthenticated()
                     .and()
                 .exceptionHandling()
-                    .authenticationEntryPoint(http401AuthenticationEntryPoint())
-                    .and()
-                .sessionManagement()
-                    .sessionCreationPolicy(SessionCreationPolicy.STATELESS);
+                    .authenticationEntryPoint(http401AuthenticationEntryPoint());

Review Comment:
   Thanks for the note @thenatog. The HTTP Request Logging on NiFi provides HTTP status code details for each URL requested, and Spring Security debug logging could be enabled for additional troubleshooting. With that background, however, it would be worthwhile to consider some of kind of error message string in certain cases. The Authentication Entry Point on NiFi has a few more scenarios to handle, but it sounds worth considering in a follow-on issue.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org