Known issue : SSO login conflict with Bluebeam Revu

[MostafaElAyoubi]

Describe the bug
When trying to login with SSO, and with Bluebeam revu plugin installed in Revit 2024 or older, the following error message appears and Orkestra isn't able to login.

Logging in with email and password is fine.

Desktop (please complete the following information):

• Revit Version : 2024 or older
• Bluebeam Version : 23.1.30 (issue might be happening with other versions, this is the one we were able to reproduce the issue with)
• Orkestra Version : 1.9.2 (issue might be happening with other versions, this is the one we were able to reproduce the issue with)

In Which context did it happen (please select from the following list) :
Orkestra Revit Addin

Additional context
The Orkestra team is currently working on figuring out a fix for this.

[DesignerDustin]

Mostafa, I recommend that people just delete the bluebeam addin from Revit, lol. It produces inferior quality drawing prints anyways. Using PDF Export produces better pdfs with clear sharp lines, especially curved lines.

[MostafaElAyoubi]

We'll be quoting you on this !

[Dre-Tas]

We're having the same issue! And I know you guys are joking about it lol but I'll have to write it here for the records: unfortunately that's not a solution.
Sorry to be a party-pooper. I'm usually more fun to be around ahaha

[DesignerDustin]

Are you sure? I just deleted the bluebeam addin from my Revit addins an hour ago and Orkestra worked like new afterwards.
Delete it from here: C:\ProgramData\Autodesk\Revit\Addins\2024

[Dre-Tas]

@DesignerDustin sorry for the confusion. What I mean by saying that "it's not a solution" is that, yes, surely removing bluebeam makes Orkestra work again, but that's not how this issue should be solved. The two applications should be able to co-exist.
Some firms might just be able to tell everyone "just uninstall bluebeam", but for us for example that's not an option.

[MostafaElAyoubi]

For sur @Dre-Tas 😄 . An update on this is that our next SSO move - with enabling SSO in the web app as its main goal - will solve this as a side effect. We've moved this up in our schedule but it unfortunately will take a little time.

[Dre-Tas]

Thanks for the update @MostafaElAyoubi
When you say that'll take a little time, how long are we expecting? So I can plan ahead.
And what's the suggestion in the meantime? Should we roll back to 1.8?

[MostafaElAyoubi]

I'd be curious to know if you're indeed able to avoid this with 1.8.3!
It's hard to give a precise timeline but it's something we should be able to have out in January 2025.

[Dre-Tas]

I'll let you know if 1.8.3 fixes it. Keep you in the loop

[MostafaElAyoubi]

This is now fixed in 1.9.3