Safe Config Service 2.9.0
What's Changed
Added accessControl
to Safe Apps
- Some Safe Apps might set access restrictions (eg.: for the host that is accessing those same apps). Each Safe App now includes a collection of restrictions (if any exist) for a specific Safe App, allowing the clients the possibility of handling apps that are restricted in a different way #363
- Current available types of restrictions:
NO_RESTRICTIONS
– no restrictions set for this Safe AppDOMAIN_ALLOWLIST
– only domains set in the returned collection are allowed to access the Safe App
- Clients can use the query parameter
?clientUrl=<domain>
to retrieve apps that are set to have no restrictions and restricted to thatdomain
GET /api/v1/safe-apps/
{
"accessControl": {
"type": "NO_RESTRICTIONS" // No restrictions for this safe app
},
}
GET /api/v1/safe-apps/
{
"accessControl": {
"type": "DOMAIN_ALLOWLIST",
"value": [
"http://domain.com" // This domain is the only one allowed to access this Safe App. Accessing from any other is not guaranteed to work
]
}
}
OTP / 2 Factor Authentication Support
- Added support for OTP in the Admin Panel – if enabled, a OTP should be configured for each user that wants to access the admin panel #371
- OTP is enabled by default but can be changed via
DJANGO_OTP_ADMIN
– the entry documentation is under.env.sample
Restrict sizes of uploaded native currency logo dimensions
- Sizes of currency logo dimensions are now restricted to
512x512
#374
Other Changes
- Bump docker/login-action from 1.11.0 to 1.12.0 in #375
- Bump boto3 from 1.20.25 to 1.20.26 in #377
- Bump mypy from 0.920 to 0.930 in #376
- Bump faker from 10.0.0 to 11.0.0 in #378
- Bump types-requests from 2.26.2 to 2.26.3 in #379
- Bump faker from 11.0.0 to 11.1.0 in #381
- Bump psycopg2-binary from 2.9.2 to 2.9.3 in #382
- Bump pillow from 8.4.0 to 9.0.0 in #383
- Bump service version to 2.9.0 in #385
- Bump Django from 3.2.10 to 4.0 in #380
Full Changelog: v2.8.1...v2.9.0