AnsweredAssumed Answered

Identity Collector on R80.20 Mgmt & R77.30 GW

Question asked by Roger De Jonckheere on May 30, 2018
Latest reply on May 31, 2018 by Houssameddine Zeghlache

Like • Show 3 Likes3
Comment • 4

Hi all,

I'm failing while trying to configure the identity collector using a R80.20 EA Mgmt and R77.30 Gateways with JHF317. As soon as I'm changing the product version of the gateway to R77.30 in SmartDashboard, the possibility to configure the IDC in the Identity Awareness Section of the cluster config is gone... but is back, as soon as I change the product version to R80.10. In the documents, it's written that R77.30 gateways from JHF308++ are supported to use with IDC.

Has anyone been able to do that? Am I doing something wrong? :-)

Regards

Roger

Houssameddine Zeghlache May 30, 2018 10:08 AM

Correct Answer

In R77.30 and lower version, I believe you should configure the collector as Terminal server. Please check this sk

Identity Collector fails to connect / add / edit a Security Gateway

I think what they mean by support, might some code enhancement in the pdpd daemon which communicate with the identity sources like IDC. The new IDC supports other things like parsing syslog messages and extract identities from it. I believe pdpd should know about the new capabilities of the collector. you will not see the change in the gui.

Thanks

See the reply in context

No one else had this question

Outcomes

Houssameddine Zeghlache May 30, 2018 10:08 AM

In R77.30 and lower version, I believe you should configure the collector as Terminal server. Please check this sk

Identity Collector fails to connect / add / edit a Security Gateway

Thanks

2 people found this helpful

Actions

Kaspars Zibarts @ Houssameddine Zeghlache on May 30, 2018 9:50 PM

That's absolutely correct answer - use Terminal server and it works like a charm. Just remember to tick the box for pre R80.10 gateway in IDC

Actions

Roger De Jonckheere @ Houssameddine Zeghlache on May 31, 2018 1:10 AM

Thanks for your answer, you're right. I found the same solution deep in some documentation shortly after I posted this question and set it up like this. Unfortunaly, I can't say if it's finally working because I had to request a valid certificate for the gateway first and I'm waiting for that. But lets be optimistic :-)

Actions

Houssameddine Zeghlache @ Roger De Jonckheere on May 31, 2018 7:03 AM

It should work with the self signed certificate. when you establish the connectivity from the IDC to the gateway you must accept the finger prints of the cert.

3 people found this helpful

Actions

4 Replies

Houssameddine Zeghlache May 30, 2018 10:08 AM
Unmark Correct
Correct Answer
In R77.30 and lower version, I believe you should configure the collector as Terminal server. Please check this sk
Identity Collector fails to connect / add / edit a Security Gateway
I think what they mean by support, might some code enhancement in the pdpd daemon which communicate with the identity sources like IDC. The new IDC supports other things like parsing syslog messages and extract identities from it. I believe pdpd should know about the new capabilities of the collector. you will not see the change in the gui.

Thanks
2 people found this helpful
Like • Show 1 Like1
Actions
- Kaspars Zibarts @ Houssameddine Zeghlache on May 30, 2018 9:50 PM
  Mark Correct
  Correct Answer
  That's absolutely correct answer - use Terminal server and it works like a charm. Just remember to tick the box for pre R80.10 gateway in IDC
  Like • Show 0 Likes0
  Actions
- Roger De Jonckheere @ Houssameddine Zeghlache on May 31, 2018 1:10 AM
  Mark Correct
  Correct Answer
  Thanks for your answer, you're right. I found the same solution deep in some documentation shortly after I posted this question and set it up like this. Unfortunaly, I can't say if it's finally working because I had to request a valid certificate for the gateway first and I'm waiting for that. But lets be optimistic :-)
  Like • Show 0 Likes0
  Actions
  - Houssameddine Zeghlache @ Roger De Jonckheere on May 31, 2018 7:03 AM
    Mark Correct
    Correct Answer
    It should work with the self signed certificate. when you establish the connectivity from the IDC to the gateway you must accept the finger prints of the cert.
    3 people found this helpful
    Like • Show 2 Likes2
    Actions

Identity Collector on R80.20 Mgmt & R77.30 GW

Outcomes

Related Content

Recommended Content