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
Current seeding mechanism is hardcoded could we have the same logic but imported from a configuration file? This would ease the trouble for devopses when deploying new instances of IS by allowing for having some parts preconfigured. Also instead of constants we should opt for options
Sth like the following:
{
"Roles": [
{
"Name" : "",
"Claims" : [],
"IsAdminRole" : true // this is for knowing which role name to configure as the main one
}
],
"Resources": [
{
"Name" : "api1",
"Scopes" : [
{
"Name": "api1",
"Claims" : [
]
}
]
}
],
"Users" : [
{
"Username" : "",
"Email" : "",
"Password" : ""
}
],
"Clients" : [
{
"ClientId" : "",
}
]
}
The text was updated successfully, but these errors were encountered:
Current seeding mechanism is hardcoded could we have the same logic but imported from a configuration file? This would ease the trouble for devopses when deploying new instances of IS by allowing for having some parts preconfigured. Also instead of constants we should opt for options
Sth like the following:
The text was updated successfully, but these errors were encountered: