To be able to do requests via API in `SECURE` mode, it is required to login as a valid user provding valid credentials (only name and password for now). This can be bypassed by starting the controller in `INSECURE` mode, but is not recommend for use cases other than development and testing.
To be able to do requests via API in `SECURE` mode, it is required to login as a valid user provding valid credentials (only name and password for now). This can be bypassed by starting the controller in `INSECURE` mode, but is not recommend for use cases other than development and testing.
For now there is a mechanism to create one default admin user with all permissions if there is no user available in storage. The password for this newly created user is printed in the command line for first access (or it can be found in the used file storage/database).
For now there is a mechanism to create one default admin user with all permissions if there is no user available in storage. The password for this newly created user is printed in the command line for first access.
The json file contains example roles with their permissions, to use with goSDN. The permissions in the admin role might be outdated this depends on changes of the API that might have been done since creating or last updating the file. Feel free to add missing permissions to admin if that's the case.
The json file contains example roles with their permissions, to use with goSDN. The permissions in the admin role might be outdated this depends on changes of the API that might have been done since creating or last updating the file. Feel free to add missing permissions to admin if that's the case.
For now one admin role gets added during the start-up process of the controller if there are no roles available. Roles are required for the authorization mechanism in `SECURE` mode to work. For now new roles can be added **only** in `INSECURE` mode. This is the case until we find out how to add tokens in form of metadata within a go context when using programs like `Postman`.
For now one admin role gets added during the start-up process of the controller if there are no roles available. Roles are required for the authorization mechanism in `SECURE` mode to work. For now new roles can be added **only** in `INSECURE` mode. This is the case until we find out how to add tokens in form of metadata within a go context when using programs like `Postman`.
