Secure Connect Gateway

[WilliamDLB]

We have just enabled the SCG integration to OME using the Adapter.  But when you define an adapter you can only add one Credential Profile.   A Credential Profile can only have one credential of each type.

So the one iDRAC that OME is configured with that has a password that matches the one iDRAC credential we can put into the Credential Profile for the Adapter to OME comes up as Success.  All the other iDRACs (which all have unique passwords *of course*) come up as Failed.

Did I miss something or is the SCG credential concept terribly broken?   If we can't apply individual credentials through the Adapter to OME, we will have to revert to the OME plug-in and drop all the PowerEdge systems from SCG.

[DELL-Chris H · Accepted solution]

WilliamDLB,

You are correct, SCG integration into OME only allows for 1 credential in the credential profile, so if the situation is that they all have unique passwords, then the options would be either
1) Use OME-Services plugin
or 
2) Discover each device in SCG manually

Let me know if this helps.

[WilliamDLB]

Thanks for confirming this rather unhelpful way that the OME integration works.  I can see also that as it implies that SCG is any case is communicating directly to the device and not using OME as the broker through an API that it requires SCG to be 'inside' the same perimeter as OME.  I can see cases where there might be multiple OME systems with access to a separate management LAN for out-of-band interfaces, linking back to an SCG that has the outbound access but no connection to the out-of-band interfaces.

That clearly isn't the design so SCG is rather less useful than it might be, but we'll live with it for now and try to work around the limitations.