Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
5 edited body
source | link

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "local box""localhost", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openidOpenID Connect identity provider is running in a vm behind a NAT, which has external external port 10888 forwarded to its port 443. Forwarding is working fine fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce doesn't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "local box", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openid provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding is working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce doesn't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "localhost", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My OpenID Connect identity provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding is working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce doesn't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

4 added 5 characters in body
source | link

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "local box", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openid provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding is working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce don'tdoesn't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "local box", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openid provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce don't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "local box", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openid provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding is working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce doesn't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

3 added 179 characters in body
source | link

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "local box", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openid provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce don't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use.

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openid provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce don't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

Sorry for kicking this dead horse, I've seen this question asked before. The problem is that answers to it are of no use, it has nothing to do with the fact that it's a "local box", until parties can talk to each other using the protocol (i.e. ports are forwarded, redirections are correctly set etc)

I'm currently facing the same problem, and posted my findings on Salesforce's forums (for some reason I can't access their issue reporting system, so can't ask them directly), but it didn't help to resolve it.

To make long story short:

  1. My openid provider is running in a vm behind a NAT, which has external port 10888 forwarded to its port 443. Forwarding working fine, I tested it.
  2. 1st phase of openid connect protocol completes successfully, authz code is issued and flow is returned to the callback url.
  3. Then this error about empty token follows. I tried to monitor the connections with wireshark and spotted that salesforce oidc client actually tries to connect to my IdP, gets all the way through forwarding to the vm - and isn't able to pass TLS initiation phase: when my IdP presents its certificate to it (which is self-signed), the client immediately responds with "Certificate unknown" error message, and connection is teared down.

So the real problem is that, most likely, Salesforce don't react well to self-signed certificates, presented by IdPs. Which is not very wise, as they are ubiquitously being used by developers for test purposes.

Here is a picture of what I'm talking about:

enter image description here

I've shuffled through different docs, and found nothing that could help to resolve the issue, so any help is appreciated.

2 Picture is added, list is fixed
source | link
1
source | link