All URIs are relative to https://madisonreed.looker.com:19999/api/3.0
Method | HTTP request | Description |
---|---|---|
createSamlTestConfig | POST /saml_test_configs | Create SAML Test Configuration |
deleteSamlTestConfig | DELETE /saml_test_configs/{test_slug} | Delete SAML Test Configuration |
fetchAndParseSamlIdpMetadata | POST /fetch_and_parse_saml_idp_metadata | Parse SAML IdP Url |
ldapConfig | GET /ldap_config | Get LDAP Configuration |
parseSamlIdpMetadata | POST /parse_saml_idp_metadata | Parse SAML IdP XML |
samlConfig | GET /saml_config | Get SAML Configuration |
samlTestConfig | GET /saml_test_configs/{test_slug} | Get SAML Test Configuration |
testLdapConfigAuth | PUT /ldap_config/test_auth | Test LDAP Auth |
testLdapConfigConnection | PUT /ldap_config/test_connection | Test LDAP Connection |
testLdapConfigUserAuth | PUT /ldap_config/test_user_auth | Test LDAP User Auth |
testLdapConfigUserInfo | PUT /ldap_config/test_user_info | Test LDAP User Info |
updateLdapConfig | PATCH /ldap_config | Update LDAP Configuration |
updateSamlConfig | PATCH /saml_config | Update SAML Configuration |
SamlConfig createSamlTestConfig(body)
Create SAML Test Configuration
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = new LookerApi30Reference.SamlConfig(); // {SamlConfig} SAML test config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.createSamlTestConfig(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | SamlConfig | SAML test config |
No authorization required
- Content-Type: application/json
- Accept: application/json
'String' deleteSamlTestConfig(testSlug)
Delete SAML Test Configuration
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var testSlug = "testSlug_example"; // {String} Slug of test config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.deleteSamlTestConfig(testSlug, callback);
Name | Type | Description | Notes |
---|---|---|---|
testSlug | String | Slug of test config |
'String'
No authorization required
- Content-Type: application/json
- Accept: application/json
SamlMetadataParseResult fetchAndParseSamlIdpMetadata(body)
Parse SAML IdP Url
Note that this requires that the url be public or at least at a location where the Looker instance can fetch it without requiring any special authentication.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = "body_example"; // {String} SAML IdP metadata public url
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.fetchAndParseSamlIdpMetadata(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | String | SAML IdP metadata public url |
No authorization required
- Content-Type: text/plain
- Accept: application/json
LDAPConfig ldapConfig
Get LDAP Configuration
Looker can be optionally configured to authenticate users against an Active Directory or other LDAP directory server. LDAP setup requires coordination with an administrator of that directory server.
Only Looker administrators can read and update the LDAP configuration.
Configuring LDAP impacts authentication for all users. This configuration should be done carefully.
Looker maintains a single LDAP configuration. It can be read and updated. Updates only succeed if the new state will be valid (in the sense that all required fields are populated); it is up to you to ensure that the configuration is appropriate and correct).
LDAP is enabled or disabled for Looker using the enabled field.
Looker will never return an auth_password field. That value can be set, but never retrieved.
See the Looker LDAP docs for additional information.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.ldapConfig(callback);
This endpoint does not need any parameter.
No authorization required
- Content-Type: application/json
- Accept: application/json
SamlMetadataParseResult parseSamlIdpMetadata(body)
Parse SAML IdP XML
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = "body_example"; // {String} SAML IdP metadata xml
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.parseSamlIdpMetadata(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | String | SAML IdP metadata xml |
No authorization required
- Content-Type: text/plain
- Accept: application/json
SamlConfig samlConfig
Get SAML Configuration
Looker can be optionally configured to authenticate users against a SAML authentication server. SAML setup requires coordination with an administrator of that server.
Only Looker administrators can read and update the SAML configuration.
Configuring SAML impacts authentication for all users. This configuration should be done carefully.
Looker maintains a single SAML configuation. It can be read and updated. Updates only succeed if the new state will be valid (in the sense that all required fields are populated); it is up to you to ensure that the configuration is appropriate and correct).
SAML is enabled or disabled for Looker using the enabled field.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.samlConfig(callback);
This endpoint does not need any parameter.
No authorization required
- Content-Type: application/json
- Accept: application/json
SamlConfig samlTestConfig(testSlug)
Get SAML Test Configuration
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var testSlug = "testSlug_example"; // {String} Slug of test config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.samlTestConfig(testSlug, callback);
Name | Type | Description | Notes |
---|---|---|---|
testSlug | String | Slug of test config |
No authorization required
- Content-Type: application/json
- Accept: application/json
LDAPConfigTestResult testLdapConfigAuth(body)
Test LDAP Auth
This tests that the connection is possible and that a 'server' account to be used by Looker can authenticate to the LDAP server given connection and authentication information.
connection_host, connection_port, and auth_username, are required. connection_tls and auth_password are optional.
Example:
{
\"connection_host\": \"ldap.example.com\",
\"connection_port\": \"636\",
\"connection_tls\": true,
\"auth_username\": \"cn=looker,dc=example,dc=com\",
\"auth_password\": \"secret\"
}
Looker will never return an auth_password. If this request omits the auth_password field, then the auth_password value from the active config (if present) will be used for the test.
The active LDAP settings are not modified.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = new LookerApi30Reference.LDAPConfig(); // {LDAPConfig} LDAP Config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.testLdapConfigAuth(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | LDAPConfig | LDAP Config |
No authorization required
- Content-Type: application/json
- Accept: application/json
LDAPConfigTestResult testLdapConfigConnection(body)
Test LDAP Connection
This tests that the connection is possible given a connection_host and connection_port.
connection_host and connection_port are required. connection_tls is optional.
Example:
{
\"connection_host\": \"ldap.example.com\",
\"connection_port\": \"636\",
\"connection_tls\": true
}
No authentication to the LDAP server is attempted.
The active LDAP settings are not modified.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = new LookerApi30Reference.LDAPConfig(); // {LDAPConfig} LDAP Config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.testLdapConfigConnection(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | LDAPConfig | LDAP Config |
No authorization required
- Content-Type: application/json
- Accept: application/json
LDAPConfigTestResult testLdapConfigUserAuth(body)
Test LDAP User Auth
This test accepts a full LDAP configuration along with a username/password pair and attempts to authenticate the user with the LDAP server. The configuration is validated before attempting the authentication.
Looker will never return an auth_password. If this request omits the auth_password field, then the auth_password value from the active config (if present) will be used for the test.
test_ldap_user and test_ldap_password are required.
The active LDAP settings are not modified.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = new LookerApi30Reference.LDAPConfig(); // {LDAPConfig} LDAP Config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.testLdapConfigUserAuth(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | LDAPConfig | LDAP Config |
No authorization required
- Content-Type: application/json
- Accept: application/json
LDAPConfigTestResult testLdapConfigUserInfo(body)
Test LDAP User Info
This test will let you easily test the mapping for user properties and roles for any user without needing to authenticate as that user.
This test accepts a full LDAP configuration along with a username and attempts to find the full info for the user from the LDAP server without actually authenticating the user. So, user password is not required.The configuration is validated before attempting to contact the server.
test_ldap_user is required.
The active LDAP settings are not modified.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = new LookerApi30Reference.LDAPConfig(); // {LDAPConfig} LDAP Config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.testLdapConfigUserInfo(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | LDAPConfig | LDAP Config |
No authorization required
- Content-Type: application/json
- Accept: application/json
LDAPConfig updateLdapConfig(body)
Update LDAP Configuration
Configuring LDAP impacts authentication for all users. This configuration should be done carefully.
Only Looker administrators can read and update the LDAP configuration.
LDAP is enabled or disabled for Looker using the enabled field.
It is highly recommended that any LDAP setting changes be tested using the APIs below before being set globally.
See the Looker LDAP docs for additional information.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = new LookerApi30Reference.LDAPConfig(); // {LDAPConfig} LDAP Config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.updateLdapConfig(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | LDAPConfig | LDAP Config |
No authorization required
- Content-Type: application/json
- Accept: application/json
SamlConfig updateSamlConfig(body)
Update SAML Configuration
Configuring SAML impacts authentication for all users. This configuration should be done carefully.
Only Looker administrators can read and update the SAML configuration.
SAML is enabled or disabled for Looker using the enabled field.
It is highly recommended that any SAML setting changes be tested using the APIs below before being set globally.
var LookerApi30Reference = require('looker-api-3');
var apiInstance = new LookerApi30Reference.AuthApi()
var body = new LookerApi30Reference.SamlConfig(); // {SamlConfig} SAML Config
var callback = function(error, data, response) {
if (error) {
console.error(error);
} else {
console.log('API called successfully. Returned data: ' + data);
}
};
api.updateSamlConfig(body, callback);
Name | Type | Description | Notes |
---|---|---|---|
body | SamlConfig | SAML Config |
No authorization required
- Content-Type: application/json
- Accept: application/json