The web application jumps to the okta login page and reports 400 after login

I want to use springboot to integrate okta’s OIDC to achieve single sign-on, and obtain some information of login users and accessToken from my springboot project to complete business requirements. However, after I build the demo, I start the project and access localhost:8080. Jump to the login page provided by okta, when I enter the user name and password configured in the console, okta pops up 400, the picture is as follows:Your request caused an error. The policy evaluation for this request failed. Please check the policy configuration.
my applications mavens dependies as follows:

com.okta.spring
okta-spring-boot-starter
1.4.0


com.okta.spring
okta-spring-sdk
1.4.0

my application.properties as folloows:
okta.oauth2.issuer=https://dev-85255207.okta.com/oauth2/default
okta.oauth2.client-id=0oajhix6taW9AZn845d7
okta.oauth2.client-secret=987654321
okta.oauth2.redirect-uri=/authorization-code/callback
AND The Sign-in redirect URLs of the project configured in my okta console are as follows:
http://localhost:8080/authorization-code/callback

And I have also authorized the access rights of this project to the users I need to access, but why will I report this 400? Is there anything I missed

Hello there,

Thank you for writing to Okta Devforum. My name is Akash, from Okta.

With regards to the issue that you are facing, it looks like you are using some old or deprecated version of the Okta Spring Boot SDK. Please refer to this page to find the latest SDK - GitHub - okta/okta-spring-boot: Okta Spring Boot Starter

In addition to that, please make sure the default custom authorization server that you are using has the Access Policy created and configured properly by referring to this article - Okta Help Center (Lightning)

If the Access Policy exist, kindly make sure that the policy is not configured in such a way that it does not block the access to the user.

Do you see any specific details in the System Logs on Okta dashboard for this request in which you are seeing the error?