-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Hiroyuki Wada edited this page Aug 29, 2024
·
6 revisions
Please check Example configuration page.
If you edit the XML directly, set the PEM as shown in the below to load it.
<connectorConfiguration xmlns:icfc="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/connector-schema-3">
...
<icfc:configurationProperties xmlns:gen500="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/bundle/jp.openstandia.connector.connector-github/jp.openstandia.connector.github.GitHubConnector">
<gen500:privateKey>-----BEGIN RSA PRIVATE KEY-----
MIIEpQIBAAKCAQEAvolV7oc2OtbDGw8Q8elj4VnZgyEp4IIj+85bI3a3ZpoU4+LL
...
yWoplzM9xuj5CyOLzKeM12EJR/sf0MOUO5tbg9uNNuDybDtRpcRbnok=
-----END RSA PRIVATE KEY-----
</gen500:privateKey>
<gen500:appId>(GitHub App ID)</gen500:appId>
...Or, if setting from the GUI, you can paste PEM with "\n" replaced by single-byte spaces.
3. The resource is up after successful configuration, but when trying to provision a user with GitHub connector resource, it causes error
Please check the following points in your GitHub Organization settings.
-
Have you enabled SAML auth in your GitHub Organization settings? This connector uses SCIM, but due to GitHub specifications, it cannot be used without enabling SAML auth.
-
Is SAML authentication successful when you run "Test SAML configuration" on GitHub?
-
Does the application for this connector registered with GitHub Apps have "Read and write access to members" permission?
