If you would like to disable Pangolin auth, you can disable the Use Platform SSO toggle.
In other words, disabling the foregoing option and hitting save should save successfully without any errors. Primarily, the Save Users & Roles button should save the configured option.
(Thanks @hhftechnology for the screenshot^)
Steps to Reproduce:
Download the latest version of the application. (v1.0.0 beta12)
Install the application via the standard process from the doc.
Create a few resources (may be 5, this bit isn't deterministic)
Navigate to the Resources page > (pick a resource) > Authentication > Hit Save Users & Roles
Try toggling the SSO switch or saving as is, but attempt to save at least 5 times.
You should see a red error banner at bottom right.
Originally created by @gokussjx on GitHub (Feb 5, 2025).
**Current Behavior:** On hitting `Save Users & Roles` button, this error pops up and the save never succeeds:
> **Failed to set roles**
> Resource with that domain already exists

**Expected Behavior:** As per the [doc](https://docs.fossorial.io/Getting%20Started/quick-setup#5-add-targets-and-authentication):
> If you would like to disable Pangolin auth, you can disable the `Use Platform SSO` toggle.
In other words, disabling the foregoing option and hitting save should save successfully without any errors. Primarily, the `Save Users & Roles` button should save the configured option.

(Thanks @hhftechnology for the screenshot^)
**Steps to Reproduce:**
1. Download the latest version of the application. (`v1.0.0 beta12`)
2. Install the application via the standard process from the doc.
3. Create a few resources (may be 5, this bit isn't deterministic)
4. Navigate to the Resources page > (pick a resource) > Authentication > Hit `Save Users & Roles`
5. Try toggling the SSO switch or saving as is, but attempt to save at least 5 times.
6. You should see a red error banner at bottom right.
**Environment:**
- OS: Ubuntu
- Application Version: v1.0.0 beta12
**Additional Information:**
- Screenshot of error message attached.
- Discord thread: [link](https://discord.com/channels/1325658630518865980/1336625963798364232/1336625963798364232)
- Bug reproducible by @hhftechnology in the channel
Hey, thanks for finding this - was a missing if statement 😑.
I patched beta.12 with a fix for this. Can you re-pull the 1.0.0-beta.12 image?
I think we might introduce some kind of early testing program for people to use pre-build versions so we can find this stuff sooner.
Edit: Seemed to only affect base domain resources.
@miloschwartz commented on GitHub (Feb 5, 2025):
Hey, thanks for finding this - was a missing if statement 😑.
I patched beta.12 with a fix for this. Can you re-pull the 1.0.0-beta.12 image?
I think we might introduce some kind of early testing program for people to use pre-build versions so we can find this stuff sooner.
Edit: Seemed to only affect base domain resources.
+1 to an eartly-testing program. Additionally, unit & regression testing would be super useful as the project gets more and more feature-rich 👀
@gokussjx commented on GitHub (Feb 5, 2025):
Can confirm, all working now, thanks!
+1 to an eartly-testing program. Additionally, unit & regression testing would be super useful as the project gets more and more feature-rich 👀
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gokussjx on GitHub (Feb 5, 2025).
Current Behavior: On hitting
Save Users & Rolesbutton, this error pops up and the save never succeeds:Expected Behavior: As per the doc:
In other words, disabling the foregoing option and hitting save should save successfully without any errors. Primarily, the
Save Users & Rolesbutton should save the configured option.(Thanks @hhftechnology for the screenshot^)
Steps to Reproduce:
v1.0.0 beta12)Save Users & RolesEnvironment:
Additional Information:
@miloschwartz commented on GitHub (Feb 5, 2025):
Hey, thanks for finding this - was a missing if statement 😑.
I patched beta.12 with a fix for this. Can you re-pull the 1.0.0-beta.12 image?
I think we might introduce some kind of early testing program for people to use pre-build versions so we can find this stuff sooner.
Edit: Seemed to only affect base domain resources.
@nixielectra commented on GitHub (Feb 5, 2025):
Latest beta.12 image fixed this issue for me, was on subdomain resource.
@manilx commented on GitHub (Feb 5, 2025):
Fixed, for me too. 👍
@gokussjx commented on GitHub (Feb 5, 2025):
Can confirm, all working now, thanks!
+1 to an eartly-testing program. Additionally, unit & regression testing would be super useful as the project gets more and more feature-rich 👀