Connect-SSOAdminServer fails with Exception

wesold commented 3 years ago

===Tested Against Environment==== vSphere Version: [6.5 U2h (b13834586), 6.7 U3h (b16243230), 6.7 U3j (b16709110)] PowerCLI Version: PowerCLI 12.0.0.15947286 PowerShell Version: 5.1.14393.2248 OS Version: Windows 10

Attempting to connect to an SSO Admin Server fails in some circumstances with the following exception:

New-Object : Exception calling ".ctor" with "4" argument(s): "One or more errors occurred." At C:\Users\Administrator\Documents\WindowsPowerShell\Modules\VMware.vSphere.SsoAdmin\VMware.vSphere.SsoAdmin.psm1:131 char:25 + $ssoAdminServer = New-Object ` + ~~~~

CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvocationException

FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand

I'm trying to identify if there are version requirements for this module out side of PowerShell Version (notes claim 5.1 supported), and VMware.VimAutomation.Common (>12.0). Are there any vCenter version requirements? Are there any differences between Embedded and External PSC?

What I'm finding is as follows:

Connecting to vCenter at 6.7 U3j without any External Identity Source configured, +Embedded PSC succeeds.
Connecting to vCenter at 6.7 U3j with an External Identity Source configured, +Embedded PSC succeeds.
Connecting to vCenter at 6.7 U3h with an External Identity Source configured, +External PSC fails as above.
Connecting to vCenter at 6.5 U2h with an External Identity Source configured, +External PSC fails as above.

If there is any additional information you'd like, please let me know.

dmilov commented 3 years ago

Hi Dan,

can you print the error details with

$error[0] | select *

wesold commented 3 years ago

PSMessageDetails : Exception : System.Management.Automation.MethodInvocationException: Exception calling ".ctor" with "4" argument(s): "One or more errors occurred." ---> System.AggregateException: One or more errors occurred. ---> System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.ServiceModel.Channels.HttpChannelFactory1.HttpRequestChannel.HttpChannelAsyncRequ est.CompleteGetResponse(IAsyncResult result) --- End of inner exception stack trace --- at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass7_01.<Crea teGenericTask>b__0(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization) --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at VMware.vSphere.LsClient.LookupServiceClient.FindServiceEndpoint(String product, String type, String endpointType) at VMware.vSphere.SsoAdminClient.SsoAdminClient..ctor(String hostname, String user, SecureString password, X509CertificateValidator serverCertificateValidator) at VMware.vSphere.SsoAdminClient.DataTypes.SsoAdminServer..ctor(String hostname, String user, SecureString password, X509CertificateValidator serverCertificateValidator) --- End of inner exception stack trace --- at System.Management.Automation.DotNetAdapter.AuxiliaryConstructorInvoke(MethodInformation methodInformation, Object[] arguments, Object[] originalArguments) at System.Management.Automation.DotNetAdapter.ConstructorInvokeDotNet(Type type, ConstructorInfo[] constructors, Object[] arguments) at Microsoft.PowerShell.Commands.NewObjectCommand.CallConstructor(Type type, ConstructorInfo[] constructors, Object[] args) TargetObject : CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvocationException FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand ErrorDetails : InvocationInfo : System.Management.Automation.InvocationInfo ScriptStackTrace : at Connect-SsoAdminServer, C:\Users\Administrator\Documents\WindowsPowerShell\Modules\ VMware.vsphere.ssoadmin\VMware.vSphere.SsoAdmin.psm1: line 131 at , : line 1 PipelineIterationInfo : {}

dmilov commented 3 years ago

The module is tested with VC 6.7 and VC 7.0 with embedded PSC. In the failing cases, the server responds with HTTP 400 Bad Request. I suspect the LookupService request searchAllSsoDomains field is missing on the 6.5 and 6.7U3h Servers

It is not needed for the purpose of this functionality though. I'll remove it and I'll ask you to try again.

dmilov commented 3 years ago

@wesold Can you try to connect with the applied fix? Thanks!

wesold commented 3 years ago

I think those updates have resolved the issue. I can now connect to 6.5 U2h, 6.7 U3h, and 6.7 U3j. Previously, for the vCenter with the External PSCs, I had attempted to connect to both the vCenter and the PSC with no success. After this change, I'm able to connect to the External PSC's Lookup Service.

Confirmed I can connect to:

6.7 with Embedded PSC
6.7 with External PSC
6.5 with External PSC

dmilov commented 3 years ago

good.

DijoJose1 commented 3 years ago

Hello Dimilov, I am getting the same error while connecting to VC with version 6.7. Do we have any fix for 6.7 version. It is working fine for 7.0 version.

Connect-SsoAdminServer : One or more errors occurred. At line:1 char:14

... connected = Connect-SsoAdminServer -Server $vcenterName -User $adminU ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
    FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Connect-SsoAdminServer

Thanks and Regards, Dijo Jose

philiprusinov commented 3 years ago

Hello Dimilov, I am getting the same error while connecting to VC with version 6.7. Do we have any fix for 6.7 version. It is working fine for 7.0 version.

Connect-SsoAdminServer : One or more errors occurred. At line:1 char:14
... connected = Connect-SsoAdminServer -Server $vcenterName -User $adminU ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
    FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Connect-SsoAdminServer
Thanks and Regards, Dijo Jose

I can confirm that latest version of module (1.2.3.) works fine for me on VCSA 7.0 and 6.7 U3.

DijoJose1 commented 3 years ago

Thank you so much for the quick response.

This looks strange. I used the latest release. But still getting the error.

writeErrorStream : True PSMessageDetails : Exception : Microsoft.PowerShell.Commands.WriteErrorException: One or more errors occurred. TargetObject : CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Connect-SsoAdminServer ErrorDetails : InvocationInfo : System.Management.Automation.InvocationInfo ScriptStackTrace : at Connect-SsoAdminServer, D:\Script\VC-AdminPasswordReset\PowerCLI-Example-Scripts-master\ Modules\VMware.vSphere.SsoAdmin\VMware.vSphere.SsoAdmin.psm1: line 157 at , : line 1 PipelineIterationInfo : {0, 1}

I am able to connect to 7.0 vcenters: PS C:\Windows\system32> $connected = Connect-SsoAdminServer -Server $vcenterName -User $adminUser -Password $oldPwd -SkipCertificateCheck

PS C:\Windows\system32> $connected.IsConnected True

Could you please let me know what can be the issue?

Thanks & Regards, Dijo Jose.

dmilov commented 3 years ago

can you get the exception details:

$error[0].Exception | Select *

DijoJose1 commented 3 years ago

PS C:\Windows\system32> $connected = Connect-SsoAdminServer -Server $vcenterName -User $adminUser -Password $oldPwd -SkipCertificateCheck -Verbose Connect-SsoAdminServer : One or more errors occurred. At line:1 char:14

... connected = Connect-SsoAdminServer -Server $vcenterName -User $adminU ...


+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Connect-SsoAdminServer

PS C:\Windows\system32> $error[0].Exception | Select *

Message : One or more errors occurred. Data : {} InnerException : TargetSite : StackTrace : HelpLink : Source : HResult : -2146233087

PS C:\Windows\system32>

DijoJose1 commented 3 years ago

VC version: EsXi 6.7 Express Patch 14 Esxi670-202004001 2020-04-07 15820472

The latest patch will work for this version. right?

dmilov commented 3 years ago

It will be hard to me to deploy this build and test. I can suggest two thing to get more info about the error.

Can you try to run the same on PowerShell 7.0?
Can you try to edit the module code a bit to get the error because the last error looks like error that occurs in Write-Error Remove the try{}catch{} block here https://github.com/vmware/PowerCLI-Example-Scripts/blob/bffb3f763017749f22957bd28fb5a76e171da541/Modules/VMware.vSphere.SsoAdmin/VMware.vSphere.SsoAdmin.psm1#L157

and let's see the error details then.

DijoJose1 commented 3 years ago

Please see the error details. Upgrading the PS version from 5.1 to 7 will take some time since I need to get the approval to upgrade the version. Error Details:

New-Object : Exception calling ".ctor" with "4" argument(s): "One or more errors occurred." At D:\Script\VC-AdminPasswordReset\PowerCLI-Example-Scripts-master\Modules\VMware.vSphere.SsoAdmin\VMware.vSphere.SsoAdmin.p sm1:149 char:28

$ssoAdminServer = New-Object `


+ CategoryInfo          : InvalidOperation: (:) [New-Object], MethodInvocationException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand

PS C:\Windows\system32> $error[0].Exception | Select *

ErrorRecord : Exception calling ".ctor" with "4" argument(s): "One or more errors occurred." WasThrownFromThrowStatement : False Message : Exception calling ".ctor" with "4" argument(s): "One or more errors occurred." Data : {} InnerException : System.AggregateException: One or more errors occurred. ---> System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.ServiceModel.Channels.HttpChannelFactory1.HttpRequestChannel.HttpChannelAsyncReq uest.CompleteGetResponse(IAsyncResult result) --- End of inner exception stack trace --- at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass7_01.<Cre ateGenericTask>b0(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization) --- End of inner exception stack trace --- at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at VMware.vSphere.LsClient.LookupServiceClient.FindServiceEndpoint(String product, String type, String endpointType) at VMware.vSphere.SsoAdminClient.SsoAdminClient..ctor(String hostname, String user, SecureString password, X509CertificateValidator serverCertificateValidator) at VMware.vSphere.SsoAdminClient.DataTypes.SsoAdminServer..ctor(String hostname, String user, SecureString password, X509CertificateValidator serverCertificateValidator) ---> (Inner Exception #0) System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.ServiceModel.Channels.HttpChannelFactory1.HttpRequestChannel.HttpChannelAsyncReq uest.CompleteGetResponse(IAsyncResult result) --- End of inner exception stack trace --- at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>cDisplayClass7_01.<Cre ateGenericTask>b__0(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task`1 promise, Boolean requiresSynchronization)<---

TargetSite : System.Object AuxiliaryConstructorInvoke(System.Management.Automation.MethodInformation, System.Object[], System.Object[]) StackTrace : at System.Management.Automation.DotNetAdapter.AuxiliaryConstructorInvoke(MethodInformation methodInformation, Object[] arguments, Object[] originalArguments) at System.Management.Automation.DotNetAdapter.ConstructorInvokeDotNet(Type type, ConstructorInfo[] constructors, Object[] arguments) at Microsoft.PowerShell.Commands.NewObjectCommand.CallConstructor(Type type, ConstructorInfo[] constructors, Object[] args) HelpLink : Source : System.Management.Automation HResult : -2146233087

dmilov commented 3 years ago

VC version: EsXi 6.7 Express Patch 14 Esxi670-202004001 2020-04-07 15820472

The latest patch will work for this version. right?

Tested with VC 6.7 U3. It works fine. The build you have provided above is ESXi, are you sure you're not calling the connect cmdlet against ESXi server?

DijoJose1 commented 3 years ago

VC version: EsXi 6.7 Express Patch 14 Esxi670-202004001 2020-04-07 15820472 The latest patch will work for this version. right?

Tested with VC 6.7 U3. It works fine. The build you have provided above is ESXi, are you sure you're not calling the connect cmdlet against ESXi server?

I can confirm it is vCenter. Able to connect to V 7.0 VC; but not to 6.7

DijoJose1 commented 3 years ago

vCenter Version: Version 6.7.0 Build 15976728

DijoJose1 commented 3 years ago

Hello Dmilov,

Please see the vcenter versions: Version 6.7.0 Build 15976728

Please confirm if Connect-SSOAdminServer works with this version. Do we need to upgrade the version?

Thanks & Regards, Dijo Jose.

From: dmilov @.> Sent: Thursday, March 25, 2021 10:27 PM To: vmware/PowerCLI-Example-Scripts @.> Cc: Dijo Jose @.>; Comment @.> Subject: Re: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401)

VC version: EsXi 6.7 Express Patch 14 Esxi670-202004001 2020-04-07 15820472

The latest patch will work for this version. right?

Tested with VC 6.7 U3. It works fine. The build you have provided above is ESXi, are you sure you're not calling the connect cmdlet against ESXi server?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/vmware/PowerCLI-Example-Scripts/issues/401#issuecomment-807094773, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATMX7WXRW2DAFM7YYUJP2UDTFNTPPANCNFSM4UT3VU2A.

The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

dmilov commented 3 years ago

Deployed this VC build today. Works on both PS 5.1 and PS 7 with VMware.vSphere.SsoAdmin 1.2.3 Tested VC 6.5 as well. It works on 6.5, 6.7, 7.0. I consider the above as a VC server issue.

DijoJose1 commented 3 years ago

Thank you so much for the updates Dimilov.

Do you think it is a permission issue? Or VC installation/upgrade issue? Or connectivity issue between server and our test server (both in same network)? Do you think if there is any kind of additional permissions we have to set in server side?

I don't think it is a permission issue. The server reports bad request which is rather the endpoint doesn't recognize the request. I assume it is some kind of specific deployment issue.

dmilov commented 3 years ago

Hi DijoJose1, I intended to reply to your comment but edited it by mistake.

I don't think it is a permission issue. The server reports Bad Request which is rather the endpoint doesn't recognize the request. I assume it is some kind of specific deployment issue.

DijoJose1 commented 3 years ago

Thank you so much for the response. I am able to connect from vsphere client (from browser) and also using the Connect-VIServer from powershell. Do you still think that it is a deployment issue?

Thanks & Regards, Dijo Jose

From: dmilov @.> Sent: Thursday, April 22, 2021 11:07 AM To: vmware/PowerCLI-Example-Scripts @.> Cc: Dijo Jose @.>; Comment @.> Subject: Re: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401)

Hi DijoJose1, I intended to reply to your comment but edited it by mistake.

I don't think it is a permission issue. The server reports Bad Request which is rather the endpoint doesn't recognize the request. I assume it is some kind of specific deployment issue.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/vmware/PowerCLI-Example-Scripts/issues/401#issuecomment-824552639, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATMX7WV75ASC4IQEVIRFWH3TJ6YYHANCNFSM4UT3VU2A.

The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

dmilov commented 3 years ago

Let's check the SSO logs for errors. Can you grab the latest logs of the below files from the VCSA after the failure? /var/log/vmware/sso/ssoAdminServer.log /var/log/vmware/sso/vmware-identity-sts.log

DijoJose1 commented 3 years ago

Hello Dmilov,

I couldn’t find the specified log file in my windows server (2019). Could you please let me know the logfile location in windows server?

Thanks & Regards, Dijo Jose

-- @.***D73AA2.94BB1300]

Dijo Jose | DevOps | Converged Hardware Services Automation | Compute Services

EY GDS Fifth Floor, Athulya Infopark, Infopark Campus, Cochin, Kerala , GDS - India Cell: +91 9847943821 | Email: @.*** Website: http://www.ey.com http://www.ey.com/

From: dmilov @.> Sent: Monday, April 26, 2021 10:53 AM To: vmware/PowerCLI-Example-Scripts @.> Cc: Dijo Jose @.>; Comment @.> Subject: Re: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401)

Let's check the SSO logs for errors. Can you grab the latest logs of the below files from the VCSA after the failure? /var/log/vmware/sso/ssoAdminServer.log /var/log/vmware/sso/vmware-identity-sts.log

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/vmware/PowerCLI-Example-Scripts/issues/401#issuecomment-826511067, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATMX7WTRPK727VMHOABLKL3TKT2D7ANCNFSM4UT3VU2A.

The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

dmilov commented 3 years ago

Hi Dijo, Is it a windows VC? The log files are on the VC machine, if this one is on Windows the log files should be in %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\SSO

https://kb.vmware.com/s/article/2110014

If it is VCSA they are under /var/log/vmware/sso/

DijoJose1 commented 3 years ago

Hello Dmilov,

PFA the logs from VC.

Thanks & Regards, Dijo Jose

From: dmilov @.> Sent: Monday, April 26, 2021 4:59 PM To: vmware/PowerCLI-Example-Scripts @.> Cc: Dijo Jose @.>; Comment @.> Subject: Re: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401)

Hi Dijo, Is it a windows VC? The log files are on the VC machine, if this one is on Windows the log files should be in %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\SSO

https://kb.vmware.com/s/article/2110014

If it is VCSA they are under /var/log/vmware/sso/

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/vmware/PowerCLI-Example-Scripts/issues/401#issuecomment-826759731, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATMX7WUFMIIXEOICDZDFPKTTKVE6BANCNFSM4UT3VU2A.

The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

DijoJose1 commented 3 years ago

No logs in ssoAdminServer.log.

From: Dijo Jose Sent: Monday, April 26, 2021 7:45 PM To: 'vmware/PowerCLI-Example-Scripts' @.>; vmware/PowerCLI-Example-Scripts @.> Cc: Comment @.***> Subject: RE: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401)

Hello Dmilov,

PFA the logs from VC.

Thanks & Regards, Dijo Jose

From: dmilov @.**@.>> Sent: Monday, April 26, 2021 4:59 PM To: vmware/PowerCLI-Example-Scripts @.**@.>> Cc: Dijo Jose @.**@.>>; Comment @.**@.>> Subject: Re: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401)

Hi Dijo, Is it a windows VC? The log files are on the VC machine, if this one is on Windows the log files should be in %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\SSO

https://kb.vmware.com/s/article/2110014

If it is VCSA they are under /var/log/vmware/sso/

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/vmware/PowerCLI-Example-Scripts/issues/401#issuecomment-826759731, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATMX7WUFMIIXEOICDZDFPKTTKVE6BANCNFSM4UT3VU2A.

The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

dmilov commented 3 years ago

are there entries in the vmware-identity-sts.log ?

DijoJose1 commented 3 years ago

Yes.. That is the one which I shared in my earlier mail. Attaching same here too…

From: dmilov @.> Sent: Monday, April 26, 2021 9:56 PM To: vmware/PowerCLI-Example-Scripts @.> Cc: Dijo Jose @.>; Comment @.> Subject: Re: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401)

are there entries in the vmware-identity-sts.log ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/vmware/PowerCLI-Example-Scripts/issues/401#issuecomment-826976703, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATMX7WUOCXLCRSPKP7MHATLTKWH3FANCNFSM4UT3VU2A.

The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

dmilov commented 3 years ago

Yes.. That is the one which I shared in my earlier mail. Attaching same here too… From: dmilov @.> Sent: Monday, April 26, 2021 9:56 PM To: vmware/PowerCLI-Example-Scripts @.> Cc: Dijo Jose @.>; Comment @.> Subject: Re: [vmware/PowerCLI-Example-Scripts] Connect-SSOAdminServer fails with Exception (#401) are there entries in the vmware-identity-sts.log ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#401 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATMX7WUOCXLCRSPKP7MHATLTKWH3FANCNFSM4UT3VU2A. … ___ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. EY is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

How do you attach them? I don't think it is possible to attach log files in the github issues? I don't see it anywhere. Do you reply to this thread by email? You can contact me on the email directly: dmilov@vmware.com

DijoJose1 commented 3 years ago

Issue Resolved. Thank you so much Dimitar for your help. Much appreciated...

vmware / PowerCLI-Example-Scripts

Connect-SSOAdminServer fails with Exception #401