In Fashion store apps we have a use case similar to a guest user. Without authentication, user can use the functionality that doesn’t have any customer resource data or any personalisation features. Such functionality includes plain catalog navigation, inspiration content or generic my feed, etc. To support such a use case, it would make sense for us to have the support for client credentials flow as stated in the spec.
An alternative could be to create a default guest-like user and get an access token through a Resource owner password credentials flow using that user. But, this is more a workaround and doesn’t seem to add any value.
In Fashion store apps we have a use case similar to a guest user. Without authentication, user can use the functionality that doesn’t have any customer resource data or any personalisation features. Such functionality includes plain catalog navigation, inspiration content or generic my feed, etc. To support such a use case, it would make sense for us to have the support for client credentials flow as stated in the spec.
An alternative could be to create a default guest-like user and get an access token through a Resource owner password credentials flow using that user. But, this is more a workaround and doesn’t seem to add any value.