Skip to content
English
MLS / Association Staff Login
  • There are no suggestions because the search field is empty.

TRIBUS / Solid Earth SAML Identity Provider (IDP) Supported Attributes

A comprehensive checklist of the standard user fields, MLS identifiers, and alternate attribute labels TRIBUS / Solid Earth supports when acting as your SAML Identity Provider (IDP).

When configuring a Single Sign-On (SSO) connection using the self-service portal where TRIBUS / Solid Earth acts as the Identity Provider (IDP), our system passes specific user data to the third-party application (the Service Provider).

Third-party vendors will frequently ask which data fields, known as SAML Attributes, our system can pass during the login handshake. This article provides a comprehensive checklist of our natively supported attributes to help you complete your vendor setup.

Standard SAML Attributes & Supported Labels

The following table details all of the data attributes natively supported and included in our SAML payloads. This list also includes alternate capitalized labels specifically mapped out-of-the-box to support strict vendor requirements (such as CoreLogic Matrix, Realist, or OneHome).

Attribute Name Source Data Mapping
ams_custom_member_subclasses Can include multiple values based on board membership.
ams_mls_choices Can include multiple values based on board membership.
ams_user_type Mapped directly to the TRIBUS internal field called AMS User Type.
custom_member_subclass A 1:many Membership field, returned as an array.
email Sourced directly from the user's primary login email.
Email (Alternate Label) Sourced from the user's primary login email.
elan_email Sourced from the user's email.
elan_first_name Sourced from the user's first_name.
elan_last_name Sourced from the user's last_name.
elan_username Sourced from the user's Custom Identifier value (requires type to be set to Elan Username).
loginid (Alternate Label) Sourced from the board member's member_login_id.
member_is_assistant_to Sourced from the board member’s field of the same name.
member_key Sourced from the board member’s field of the same name.
member_login_id Sourced from the board member’s field of the same name.
member_mls_id Sourced from the board member’s field of the same name.
member_national_association_id Sourced from the board member’s field of the same name (NRDS ID).
member_state_license Sourced from the board member’s field of the same name.
Member_type Sourced from the board member’s field of the same name.
MemberFirstName (Alternate Label) Sourced from the user's first_name.
MemberLastName (Alternate Label) Sourced from the user's last_name.
MemberMlsId (Alternate Label) Sourced from the board member's member_mls_id.
MLS (Alternate Label) Sourced from the board member's source_system_name.
MlsId (Alternate Label) Sourced from the board member's source_system_name.
NRDSID (Alternate Label) Sourced from the member's member_national_association_id.
office_mls_ids Sourced from the user’s associated Offices (User > Network Office, not the MLS Office directly from the data feed).
office_names Sourced from the user’s associated Offices (User > Network Office, not the MLS Office directly from the data feed).
postal_code Sourced from the zip code in the user’s primary address (or from the zip code in the first available address if no primary is set).
ramco_guid The unique GUID from the RAMCO Member (Contact Entity).
source_system_id Sourced from the board member’s field of the same name.
source_system_member_key Sourced from the board member’s field of the same name.
source_system_name Sourced from the board member’s field of the same name.

Custom Attribute Requirements

If your vendor states that they strictly require complex attributes outside of our standard list (such as specialized roster groups or feed specifications) , these payloads are not active by default.

Passing custom attributes requires custom development from our engineering team. If your vendor requests them, please gather their exact specifications and contact your our support team to scope out the requirement.