heiss / akt Goto Github PK

• service endpoint handles the configuration
  • user set api endpoint for the configured service
  • user configures the field, he wants to get
  • user set the event to trigger this configuration (example: interval, trigger event etc.)
  • user set the api endpoint, which expose the configured data
• the new api configuration creates a new api, which the user can consume

• can trigger authorisation process
• user can list all authorised services
• user can remove them

this format needs to handle:

• servicename
• endpoints
• client id / secrets
• datapoints
• endpoints
• jsonschema validation / openapi specification for verification for incoming and outgoing requests

First, no backend connection
Only presentation

• Admin can create new auth services
• Admin can see all services
• User can create a new authorisation for configured service
• User can see all created endpoints (groups for data)
• User can create new endpoint
• User can see all datapoints
• User can create new datapoints
• Loginscreen

needs to be done:

• service saves things like: api client_id, client_secret, redirect_url, refresh token api endpoint url , api endpoint url
• respects expiration time and handles refresh token