ResearchCave.Identity.Browser (1.1.67)
Installation
dotnet nuget add source --name ResearchCave --username your_username --password your_token https://git.researchcave.com/api/packages/ResearchCave/nuget/index.jsondotnet add package --source ResearchCave --version 1.1.67 ResearchCave.Identity.BrowserAbout this package
Shared browser controls for selecting ResearchCave members through application-owned Identity search endpoints.
ResearchCave.Identity.Browser
Shared, framework-neutral browser controls for selecting ResearchCave members. The package serves its assets from the host application; it does not expose Identity data itself.
Host setup
using ResearchCave.Identity.Browser;
app.MapResearchCaveIdentityBrowser();
Load the assets on pages that use the picker:
<link rel="stylesheet" href="/researchcave-identity/v1/member-search.css">
<script src="/researchcave-identity/v1/member-search.js"></script>
The host must provide an authenticated, same-origin search endpoint. It should call IUserService.SearchAsync with only Username | Name, apply domain authorization and candidate filtering, and return:
{
"users": [
{
"subjectId": "00000000-0000-0000-0000-000000000000",
"userName": "member",
"displayName": "Member Name",
"profileImageUrl": null
}
]
}
Configure the control with data-researchcave-member-search and data-endpoint. Its required descendants are identified by the data-member-query, data-member-value, data-member-results, data-member-selected, and data-member-clear attributes. See ResearchCave Economy's administrative mint UI for complete markup.
The selected subject ID is untrusted input. Resolve it again through IUserService.ResolveBySubjectIdAsync and repeat domain authorization before any state-changing operation.