You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To build the custom types and communicate with the SigAuth Core the sdk needs the following fields
ISSUER_URL, APP_ID, APP_TOKEN
This is information wether be stored inside the projects ´.env´ file or in a seperate config. To invoke separation of concerns I would suggest using a custom config.
This config can be easily custom typed and extended later on to improve usability
URL of your SigAuth instance; identifies the authentication server.
appId
string
UUID of the App registered in your SigAuth instance
appToken
string
random Char Token to authenticate & authorise sdk requests
While implementing the SDK I need to reimplement the AuthGuards because all interaction with the core happens through the sdk. That means every request needs to be validated by the appId and appToken.
Permissions of the Apps using the SDK are validated using the AppScopes
Session and request validation is made on the app using the sdk utilitis. That means
Checking if the accessToken is valid (automatic refresh if needed)
Each Core Action (Managing an Assets, AssetTypes & Grants) will be still authorized by the core to avoid poorly implemented apps from authorization mission critical actions
Incertain cases you might want apps to manage assets by itself this would not be possible if an account accessToken is required for authorization. Therefore I'll add a flag internalAccountAuthorization which toggles the core check of required user permissions to all actions of that request.
That means that each SDK Request needs a option object which allows to toggle the internal account authorization
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
To build the custom types and communicate with the SigAuth Core the sdk needs the following fields
ISSUER_URL, APP_ID, APP_TOKEN
This is information wether be stored inside the projects ´.env´ file or in a seperate config. To invoke separation of concerns I would suggest using a custom config.
This config can be easily custom typed and extended later on to improve usability
Current fields that could belong in such a config
{ "issuer": "https://<your-sigauth-instance-domain>", "appId": "<uuid>", "appToken": "<token", }issuerappIdappTokenWhile implementing the SDK I need to reimplement the AuthGuards because all interaction with the core happens through the sdk. That means every request needs to be validated by the appId and appToken.
internalAccountAuthorizationwhich toggles the core check of required user permissions to all actions of that request.Beta Was this translation helpful? Give feedback.
All reactions