microsoft / microsoft/DurableFunctionsMonitor
Authentication differences between isolated and in-process?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 290
- Forks
- 46
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Hello!
I have an injected mode FunctionApp hosting DfMon. Currently it's using in-process mode (DurableFunctionsMonitor.DotNetBackend v6.7.1) and I have gotten server-directed login flow working, in accordance with the documentation.
Then, I tried switching to DfMon Isolated (DurableFunctionsMonitor.DotNetIsolated v6.7.3), but then the authentication breaks (401). Are there any differences in authentication configuration between in-process and isolated? How about the redirect URL? Should it still be this for isolated:
https://<my-dfm-function-app-name>.azurewebsites.net/.auth/login/aad/callback
Any help with troubleshooting appreciated!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked authentication documentation and compare the in-process configuration with the isolated setup described in the issue. Reproduce the 401 and verify whether the /.auth/login/aad/callback redirect URL and server-directed login flow behave differently; done means isolated mode authenticates successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authentication, backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100