错误org.keycloak.adapters.OAuthRequestAuthenticator-无法将代码转换为令牌

时间:2019-12-23 08:49:06

标签: nginx single-sign-on keycloak http-status-code-403

我们的应用程序Nginx和keycloak出现问题。共有3个实例:实例1 APP,实例2 NGINX(反向代理)和实例3 Keycloak。

用户登录时,他在密钥斗篷中创建会话,但是当他返回SiAe应用程序时,即返回403。 我们进入keycloak管理控制台,看到会话已成功且已打开。但是返回到应用程序是不可能的。

日志

Nginx:

    "GET /opensat/?state=dcc1c40f-3183-4c7b-8342-f7df620cf0b3&session_state=605ba79a-ee05-4918-a96d-71466e31210a&code=fe066a17-a97a-495c-94f9-b1e5e3d6ac1f.605ba79a-ee05-4918-a96d-71466e31210a.f91920a4-3267-4de5-9788-24093a32c217 HTTP/1.1" **403 405** "https://mydomain/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0"

APP:

ERROR org.keycloak.adapters.OAuthRequestAuthenticator  - failed to turn code into token
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:196)
        at java.net.SocketInputStream.read(SocketInputStream.java:122)
        at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
        at sun.security.ssl.InputRecord.read(InputRecord.java:480)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:934)
        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
        at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573)
        at org.keycloak.adapters.SniSSLSocketFactory.createLayeredSocket(SniSSLSocketFactory.java:114)
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557)
        at org.keycloak.adapters.SniSSLSocketFactory.connectSocket(SniSSLSocketFactory.java:109)
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414)
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)

密钥斗篷:

**INFO** [org.keycloak.storage.ldap.LDAPIdentityStoreRegistry] (default task-1) Creating new LDAP Store for the LDAP storage provider: 'ldap_pre', LDAP Configuration: {pagination=[true], fullSyncPeriod=[-1], usersDn=[ou=usuarios,dc=domain,dc=es], connectionPooling=[true], cachePolicy=[DEFAULT], useKerberosForPasswordAuthentication=[false], importEnabled=[true], enabled=[true], changedSyncPeriod=[86400], bindDn=[cn=admin,dc=domain,dc=es], usernameLDAPAttribute=[uid], lastSync=[1575269470], vendor=[other], uuidLDAPAttribute=[entryUUID], connectionUrl=[ldap://MIIP:389], allowKerberosAuthentication=[false], syncRegistrations=[false], authType=[simple], debug=[false], searchScope=[1], useTruststoreSpi=[ldapsOnly], priority=[0], userObjectClasses=[inetOrgPerson, organizationalPerson, person], rdnLDAPAttribute=[cn], editMode=[WRITABLE], validatePasswordPolicy=[false], batchSizeForSync=[1000]}, binaryAttributes: []

配置:

Nginx:

location / {

        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host   $host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_pass http://IP_KEYCLOAK:8081;
}

密钥斗篷:

     ....
        <server name="default-server">
                <http-listener name="default" socket-binding="http" redirect-socket="proxyhttps" proxy-address-forwarding="true" enable-http2="true"/>
     ......
             <socket-binding name="proxy-https" port="443"/>
     .....

APP .json:

{
  "realm": "domain",
  "auth-server-url": "https://domainkeycloak/",
  "ssl-required": "none",
  "resource": "sso",
  "enable-cors" : true,
  "credentials": {
    "secret": "98236f9a-c8b1-488c-8b36-ace4f95b1aa6"
  },
  "confidential-port": 0,
  "disable-trust-manager":true,
  "allow-any-hostname" : true
}

有人可以帮助我们吗?

2 个答案:

答案 0 :(得分:0)

错误Connection reset表示应用程序无法向Keycloak服务器发出请求。由于将auth-server-url设置为https://domainkeycloak/

,因此您应该通过使用443端口登录到应用程序服务器和telnet keycloak域来进一步研究该问题。

答案 1 :(得分:0)

解决方案是将密钥库与其他Nginx分开,而不是将一个Nginx用于APP和密钥库。现在,我们有2个Nginx,并使用我们的APP运行OK密钥隐藏程序。