Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support FF Auth on Remote Instances #5014

Open
4 tasks
joepavitt opened this issue Jan 15, 2025 · 0 comments
Open
4 tasks

Support FF Auth on Remote Instances #5014

joepavitt opened this issue Jan 15, 2025 · 0 comments
Assignees
@knolleary
Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details headline Something to highlight in the release sales request requested by a sales lead size:L - 5 Sizing estimation point
Milestone
2.14

Comments

@joepavitt
Copy link
Contributor

joepavitt commented Jan 15, 2025 •
edited by knolleary
Loading

Description

We support FF User auth for Hosted Instances, but not Remote. This had been avoided originally because we cannot guarantee that Remote Instances are running in an online environment, given many customers run in closed/offline environments.

However, if customers want to use FF Auth, then we should not stop them. There is value, especially in use cases with FlowFuse Dashboard, to have FF User Auth enabled and securing remote Dashboards, especially when paired with the FF User Plugin.

Which customers would this be available to

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

Tasks
Preview Give feedback
  1. Add support for httpNodeAuth settings on devices #5068
  2. Add support for httpNodeAuth device-agent#341
@joepavitt joepavitt added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do customer request requested by customer sales request requested by a sales lead labels Jan 15, 2025
@joepavitt joepavitt added this to the 2.14 milestone Jan 15, 2025
@joepavitt joepavitt added headline Something to highlight in the release size:L - 5 Sizing estimation point and removed needs-triage Needs looking at to decide what to do labels Jan 15, 2025
@joepavitt joepavitt moved this to Scheduled in ☁️ Product Planning Jan 15, 2025
@joepavitt joepavitt moved this to Todo in 🛠 Development Jan 15, 2025
@joepavitt joepavitt moved this from Todo to Up Next in 🛠 Development Jan 17, 2025
@knolleary knolleary self-assigned this Jan 24, 2025
@knolleary knolleary moved this from Up Next to In Progress in 🛠 Development Jan 24, 2025
This was referenced Jan 30, 2025
Open
Open
@knolleary knolleary moved this from In Progress to Review in 🛠 Development Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@knolleary knolleary

Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details headline Something to highlight in the release sales request requested by a sales lead size:L - 5 Sizing estimation point
Projects
☁️ Product Planning
Status: Scheduled
🛠 Development
Status: Review
Milestone
2.14
Development

No branches or pull requests
2 participants
@knolleary @joepavitt