Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "evannielsen"

I am having a problem where even after enabling the AbpHangfireAuthorizationFilter for the hangfire dashboard I am still met with a 401 when attempting to navigate to the HangFire dashboard. This is due to the fact that the cookie is not sent with the request because the front end project and the backend api are on separate subdomains

I should clarify that we have the api in an Azure App Service by itself and the web front end in a separate Azure App Service. Thus the two pieces end up with different sub domains. The UI is still able to call the api because of the CORS setup that exists on the api.

Are the front end and back end meant to be deployed to the same sub domain? If not what are the steps I need to take to get the Hangfire dashboard up?

Question

I need to implement a one time use token where a user would send me a token as part of the query string and that would allow that request to take place under the context of the user that the token was assigned.

Does anyone know how to accomplish this in an app service? It doesn't seem like you have access to the raw request at that point.

Showing 1 to 2 of 2 entries