Content
View differences
Updated by Eric Schubert over 2 years ago
### What?
* We need to remodel and redesign the approach of storage authentication.
* Currently a storage is tightly connected to an oauth client (1-to-1 relation)
* this prevents introduction of other authentication methods for a storage
* this does not represent the current domain of one drive storages
* storages of the same tenant but for different drives usually share the same authentication application (azure app)
* creating those storages creates oauth clients, that have the exact same client credentials
* those storages could use the same client
### Why?
* creating multiple one drive storages only works due to a hack introduced in ##50871
* removing the hack helps cleaning up the code and making it more maintainable
### Hints and Ideas
* Migration to new data model
* we **probably** need to merge oauth clients with the same client Ids
* tokens issued to those clients **probably** can be merged, too, taking the latest one for each user
* We need to remodel and redesign the approach of storage authentication.
* Currently a storage is tightly connected to an oauth client (1-to-1 relation)
* this prevents introduction of other authentication methods for a storage
* this does not represent the current domain of one drive storages
* storages of the same tenant but for different drives usually share the same authentication application (azure app)
* creating those storages creates oauth clients, that have the exact same client credentials
* those storages could use the same client
### Why?
* creating multiple one drive storages only works due to a hack introduced in ##50871
* removing the hack helps cleaning up the code and making it more maintainable
### Hints and Ideas
* Migration to new data model
* we **probably** need to merge oauth clients with the same client Ids
* tokens issued to those clients **probably** can be merged, too, taking the latest one for each user