@matt-1

I will let my colleagues and community teammates chime in, having not written an Azure integration into FusionAuth as of yet. However, here is my two cents:

If FusionAuth is the source of record, you will want to review the documentation that Azure AD provides and see if you can call into FusionAuth via OAuth2 or SAML or JWT from them.

Googling azure storage blob authentication via jwt token returns many promising possibilities that look relevant.

Another wrinkle is that you are likely asking for a permissions-based model below:

Azure Storage Blog (or some intermediary) authenticates backs to FusionAuth to check whether the user is authorized for the piece of content or not.

This might require you to handroll your own solution or explore others that are prebuilt. Roles and groups are one area in FusionAuth that you could use to assign some level of access to your users. With some integration code, you could help your application determine what storage they should have access to.

https://fusionauth.io/docs/v1/tech/apis/groups/ https://fusionauth.io/docs/v1/tech/core-concepts/roles/#overview

I hope this helps and will post back if anything additional occurs to me.

Thanks
Josh

@erick

Apologies for the delay. I was not able to test the andriod portion of this very well on my Mac. Is this still an open issue for you?

Thanks,
Josh

Hi @ravikiran-sattigeri,

All applications can be retrieved via this API -

https://fusionauth.io/docs/v1/tech/apis/applications/#retrieve-an-application

The roles should be attached to the returned object under a roles array.

If you could provide some additional context around what you are attempting to accomplish, we may be able to provide additional feedback.

If you have a support contract, please file a ticket via your Zendesk or Slack channels for additional questions. Thanks!

Thanks,
Josh
FusionAuth

@faisal-jamil

You must buy another service like twilio. FusionAuth itself never sends SMSes.

Limits are set by that third party service.

@chk543

Did you end up solving this?

Hiya @maciej-wisniowski

Might make sense to file a feature request. I am not sure how likely we'd be to expose the SSO token to revocation, but we already (I believe) display it in the list of refresh tokens for a user (with an API key).

https://github.com/fusionauth/fusionauth-issues/

I can't think of many workarounds simply because there are two disjoint users (as FusionAuth sees them, because they have different login Ids) and yet you are trying to connect them (so the same human person doesn't login with two different accounts).

Hmmm. I saw a similar issue and filed a bug: https://github.com/FusionAuth/fusionauth-issues/issues/1466

Feel free to file a bug with reproducible steps in the issues repository or add comments to #1466 if you have any more info.

@richb201,

I assume you are self-hosting FusionAuth, but let me know if this is not the case.

I had to split the server into two different copies. One at researchstudyonline.com and one at staging.researchstudyonline.com.

The database is the source of state in FusionAuth. So if you copied the database, then the same users and their logins should exist in that new copy. For how you have set up FusionAuth, I would expect your staging environment would have its own database as well as production.

When I click on http://staging.researchstudynline.com/ I see that the link is broken. You may want to review your configuration and ensure that you have properly set up the new FusionAuth instance (http://staging.researchstudynline.com:9011/) and its associated database.

I am linking the appropriate documentation which may aid you further in installing a new FusionAuth instance and database:

https://fusionauth.io/docs/v1/tech/installation-guide/ https://fusionauth.io/docs/v1/tech/installation-guide/common-configuration/ https://fusionauth.io/docs/v1/tech/reference/configuration/

Lastly, there are a few different ways that you could replicate a database. One such way would be to use the pg_dump command. Once you have your dumped database, create a new empty database, and use pg_restore to import your data. Once you have your new database, you would stand up a new FusionAuth instance and point that instance at this new datastore. I would encourage you to use your search-fu to find articles that will speak to how to complete a database replication if you have any other questions about this process.

Hope this helps!

Thanks,
Josh

Thanks @joshua !