Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COWe tried something like this, and it partially works. It works perfectly fine to authenticate to the service if it's http. If we change it to https we get a SSLPeerUnverifiedException: No peer certificate. Is there any way to make an ugly hack to ignore if our server has a cert or not?
      singulars
    2. CODa_smokes, this seems to be either that you can't verify the servers cert chain or that a client cert is missing. If it's the former, then get a proper public certificate where the signing CA is in the clients keystore. If it's the latter then it will either be your code which has configured the http client to use client cert or the Samba/Apache code which might be trying to negotiate for a client cert. I haven't worked with the Samba/Apache code, but I do know how SSPI negotiates between two parties.
      singulars
    3. COIf one requests to have an auth'ed and encrypted channel, SSPI will negotiate for a authentication and encryption scheme not caring which one is selected. To limit SSPI to a specific auth or encryption scheme then you normally need to specify which ones should be part of the handshake procedure. Why am I saying this, the code you have might need some guidance to which auth and encryption scheme to use. There might be a mixup here where SSL is selected for both auth and encryption. What you want is of course SSL for encryption only and NTLM for Auth. I hope this helps in troubleshooting.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload