SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

btp-ui5-show-userinfo

A UI5 app that reads the signed-in user two ways, through the Fiori launchpad shell service and through the @sap/approuter User API, and records which environments each answers in.

Which of the two ways to the signed-in user's name and e-mail answers depends on where the app runs, and the README records that as one table per way. sap.ushell.services.UserInfo returns dummy values in local development, answers in SAP Build Work Zone, and is not available when the app is opened directly from the SAP HTML5 Application Repository service for SAP BTP; the @sap/approuter endpoints /currentUser and /attributes answer in both of those and not locally, since they are the router's own. Each table is followed by the JSON the endpoint returned, so the fields are visible without deploying: the shell service gives ID only in an S/4HANA launchpad, and /attributes adds user_uuid. The README states one boundary, that /attributes cannot retrieve custom attributes beyond the ones it lists, and cites KBA 3115516 for it.

Facts

Last push

Where it sits

Lives in
Demonstrates
AuthenticationUI5BTPAuthenticationcapabilityEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. [Authorization](capability:authorization) decides what that identity may do; [identity provisioning](capability:identity-provisioning) manages its lifecycle across systems.
Serves
Optional
@sap/approuter@sap/approuterartifactThe /currentUser and /attributes endpoints the sample reads are the application router's own, so that half of the sample needs a router in front of the app.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10
@miyasuta
maintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

Conditions

PracticalFunctional boundary

The repository publishes no licence, so reusing its code needs the author's permission.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference

As a sample

Form
A reference application

Connections3

README

quoted from miyasuta/btp-ui5-show-userinfo, read
miyasuta/btp-ui5-show-userinfo/README.mdOn GitHub

Show User Info

A sample application to explore methods for retrieving user information in UI5 applications deployed on SAP BTP.

excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/btp-ui5-show-userinfotree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domainui5, security-and-compliance
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-btp-ui5-show-userinfo
JSON
/artifacts/miyasuta-btp-ui5-show-userinfo.json
MCP
Connecting an agent