Closed Liturgist closed 1 year ago
Test-GitHubAuthenticationConfigured
just checks to see if you've configured an AccessToken. It doesn't do anything to check if the AccessToken is valid...you find that out when you use a function.
Ultimately, I think this comes down to you setting the correct ApiHostname
, my best guess is that github.com/enterprises/$CompanyName
is simply not the right value. You should check your configuration/documentation and determine what the appropriate REST endpoint is.
github.com/enterprises/$CompanyName is exactly the same string used when I login to GitHub through a web browser.
The output, including verbose output, does not provide a clue as to what the problem is. What am I missing?
The answer appears to be that for Enterprise Cloud users, the ApiHostName should not be changed from github.com
.
An org URL is https://github.com/OrgName
. This would imply that ALL organization names across ALL GitHub Enterprise Cloud customers must be unique. If not, then how are they distinguished.
If Acme Corp creates a SALES
organization, then Widget Corp would not be able to create a SALES
organization. Is that really true?
A description of your problem or question
I seem to have regressed. I thought this was working.
Test-GitHubAuthenticationConfigured returns True, but Get-GitHubUser fails. The github.com/enterprises/myco web interface shows that the_user can login. I cannot give out company information, so I have created variables to make this easier to repro.
Steps to reproduce the issue
Verbose logs showing the problem
When run as a script, the following is produced. 'theuser' can login through the web interface successfully.
Suggested solution to the issue
N/A.
Operating System
PowerShell Version
Module Version