Skip to main content

Identity as a Service (IDaaS)

To use IDaaS services, users need to have their Aspecta Identity. Each IDaaS service will require some sort of user consent depending on the service type. IDaaS services include:

Identity Auth

Identity Auth serves as an identity authorization toolkit, by which users can log in third-party websites or Apps using Aspecta Identity. Users can also use the Identity Auth service to authorize third parties to access their information.

Use case

A user logs in to a forum App with his/her Aspecta Identity and authorize the forum to access his/her profling information.

Refer to API doc.

Identity Query

Identity Query accepts queries with any of a user’s identity or accounts, and returns the user’s all associated accounts.

Use case

A user registers an eCommerce website with his/her ETH address. The website builder queries the user’s other addresses and Twitter account for better recommendation.

Refer to API doc.

Identity Profiling

Identity Query accepts queries with any of a user’s accounts or identity ID, and returns the user’s profiling information.

Use case

A user registers an eCommerce website with his/her ETH address. The website builder queries the user’s profiling, e.g., where the user is likely a geek and likes to explore new things.

Refer to API doc.

Identity Connect

Identity Connect provides queriable and editable connections between Aspecta Identity users. Connections can have multiple types, including like, friend, pre-friend, blocked, etc. Third-party builders don’t have to build connection features on their own.

Use case

A forum website queries whether two users are friends with each other. Then the website can change them into best-friends (a connection type) or non-friends (no connection).

Refer to API doc.

Identity Messaging

Identity Messaging allows users or third-parties to send messages to another Aspecta Identity user. Third-party builders don’t have to build a message service on their own.

The limits, restrictions, and notifications of messages will be the same as sending messages directly on the profile webpage.

Use case

Users log in to a Developer Community via Aspecta Identity and chat/get notifications via Aspecta Messaging. The Developer Community builders don’t have to build a message service on their own.

Refer to API doc.

Identity Search accepts queries with certain filters, and returns a list of users together with their Aspecta Identities.

Supported search filters: identity, account, profiling.

Use case

Query a list of users who have bought NFTs before.

Refer to API doc.

Identity Recommendation

Identity Recommendation accepts queries with some entities such as users, profiling tags, and returns their potential related/connected/interested entities.

Identity Recommendation can be regarded as an personalized and intelligent version of Identity Search, which obtains potentially related results rather than actually related results. For example, in a team-up App, Identity Recommendation will recommend users that can potentially form a team with you rather than already users already connected with you.

Supported recommendation types: user-user connection recommendation, user-profiling potential prediction.

Use case

Query a list of users who may be interested to buying NFTs. Query a list of users who can potentially form a team with a target user.

Refer to API doc.