-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Acesso negado a URL do QrCode payload no ambiente de desenvolvimento no QrTester. #582
Comments
O que o QR-Tester está dizendo é o servidor do Banpará recusou o acesso, com código HTTP de acesso negado... não é o do Banco Central que está negando. |
o endpoint da location precisa estar público. |
Precisa resolver esses erros de certificado ssl:
|
Tenho o mesmo erro no qrtester (Acesso negado), ao testar com openssl, não parece ter nenhum erro. Funciona normalmente quando outras instituições tentam pagar. ga@sandbox % openssl s_client -connect {{URL}}:443
CONNECTED(00000006)
depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority
verify return:1
depth=1 C = BR, O = CERTDATA SERVICOS DE INFORMACAO LTDA, CN = CERTDATA SSL EV CA [Run by the Issuer]
verify return:1
depth=0 serialNumber = 31.818.873/0001-30, jurisdictionC = BR, businessCategory = Private Organization, C = BR, ST = Minas Gerais, O = QESH INSTITUICAO DE PAGAMENTO LTDA, CN = {{URL}}
verify return:1
---
Certificate chain
0 s:serialNumber = 31.818.873/0001-30, jurisdictionC = BR, businessCategory = Private Organization, C = BR, ST = Minas Gerais, O = QESH INSTITUICAO DE PAGAMENTO LTDA, CN = {{URL}}
i:C = BR, O = CERTDATA SERVICOS DE INFORMACAO LTDA, CN = CERTDATA SSL EV CA [Run by the Issuer]
a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
v:NotBefore: Aug 3 00:00:00 2023 GMT; NotAfter: Aug 2 23:59:59 2024 GMT
1 s:C = BR, O = CERTDATA SERVICOS DE INFORMACAO LTDA, CN = CERTDATA SSL EV CA [Run by the Issuer]
i:C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority
a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA384
v:NotBefore: Mar 5 00:00:00 2020 GMT; NotAfter: Mar 5 23:59:59 2030 GMT
2 s:C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority
i:C = GB, ST = Greater Manchester, L = Salford, O = Comodo CA Limited, CN = AAA Certificate Services
a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA384
v:NotBefore: Mar 12 00:00:00 2019 GMT; NotAfter: Dec 31 23:59:59 2028 GMT
---
Server certificate
{{ decodificado no próximo bloco }}
subject=serialNumber = 31.818.873/0001-30, jurisdictionC = BR, businessCategory = Private Organization, C = BR, ST = Minas Gerais, O = QESH INSTITUICAO DE PAGAMENTO LTDA, CN = {{URL}}
issuer=C = BR, O = CERTDATA SERVICOS DE INFORMACAO LTDA, CN = CERTDATA SSL EV CA [Run by the Issuer]
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 5315 bytes and written 394 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
Protocol : TLSv1.3
Cipher : TLS_AES_256_GCM_SHA384
Session-ID: C4F68D51FC429700940E48C82868EA5DB995A5A499EE8A7A346470605941714B
Session-ID-ctx:
Resumption PSK: 31007118010DE0D39573E0C7E8F75F7B1A1C92C9959415E879579768EADF3953C24EE1FF1F97DCF59A40004FFCD84945
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 604800 (seconds)
TLS session ticket:
0000 - 1c 6b 28 7c 76 19 54 5a-ec c5 0a 57 80 1b f6 37 .k(|v.TZ...W...7
0010 - 7a 16 74 1f 9f b6 61 76-06 5d 29 6b 47 a5 d6 d5 z.t...av.])kG...
0020 - af a2 c5 cf 71 d3 25 a6-76 8d 4d d0 97 3e bc 1d ....q.%.v.M..>..
0030 - 46 ea 49 d2 99 25 0e 13-04 92 6c d9 c8 f5 4a 70 F.I..%....l...Jp
0040 - a9 5c ea 3f 47 0b 7d 47-95 6e 2b b6 4f 39 17 ae .\.?G.}G.n+.O9..
0050 - 8f c4 a5 6d a4 cd 5d 64-92 08 1f 5c ee 95 d5 f5 ...m..]d...\....
0060 - 91 35 1d c7 f5 55 69 ad-d5 16 52 07 66 9d d8 46 .5...Ui...R.f..F
0070 - c5 b8 44 e5 08 88 cd 8b-32 86 ed b3 7e 80 69 94 ..D.....2...~.i.
0080 - 2b +
Start Time: 1706739065
Timeout : 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: no
Max Early Data: 0
---
read R BLOCK Certificado decodificado do resultado acima:
|
O que diz o relatório completo de https://www.ssllabs.com/ssltest/ ? |
Mas o QRTester nem faz a chamada no meu servidor. |
Esse é só o sumário.. no relatório completo que dá para ver potenciais problemas. |
Obrigado pelo auxílio, vou aguardar a resposta do BCB no email. |
Ao tentar testar um QrCode gerado no ambiente de homologação foi encontrado um erro de acesso negado.
segue a imagem.
The text was updated successfully, but these errors were encountered: