Difference between revisions of "Cross-domain Identity Management (SCIM)"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| Line 10: | Line 10: | ||
== See also == | == See also == | ||
| + | * {{SAML}} | ||
* {{Security}} | * {{Security}} | ||
| − | + | ||
[[Category:Identity management]] | [[Category:Identity management]] | ||
Revision as of 18:40, 26 August 2021
wikipedia:System for Cross-domain Identity Management (2011, 2015) standard protocol.
- JFrog introduces initial support for the System for Cross-domain Identity Management (SCIM) protocol 2.0, to enable Enterprise and Enterprise+ customers to create, remove and disable user accounts from their choice of user management tool and automatically update the platform with these changes. Okta and Azure Active Directory (AD) have used to verify this capability
See also
- SAML, IdP, Assertion, Attribute, SCIM, Amazon Cognito, OpenID Connect (OIDC), SAML response,
SAML:EduPersonOrgDN, Assertion Consumer Service (ACS), SAML examples,Entity ID,Name ID,SAMLResponse, saml-provider - Security: Security portfolio, Security standards, Hardening, CVE, CWE, Wireless Network Hacking, vulnerability scanner, Security risk assessment, SCA, Application Security Testing, OWASP, Data leak, NIST, SANS, MITRE, Security policy, Access Control attacks, password policy, password cracking, Password manager, MFA, OTP, UTF, Firewall, DoS, Software bugs, MITM, Certified Ethical Hacker (CEH) Contents, Security+ Malware, FIPS, DLP, Network Access Control (NAC), VAPT, SIEM, EDR, SOC, pentest, PTaaS, Clickjacking, MobSF, Janus vulnerability, Back Orifice, Backdoor, CSO, CSPM, PoLP, forensic, encryption, Keylogger, Pwn2Own
Advertising:
