OTOY Forums

Could the Otoy engineers get with the site admins to please fix this broken multi-login system? One password for the forums, one for the "Octane Live"/ main customer login page (which btw does not actually have that as part of its title, so new users would not know thats what its called), another pw for the gd maya plugin and octane standalone (and more for the V2 vs V3 versions for us legacy folks).

One option would be to have ONE credential that automatically links to what the customer is entitled to. If I have a valid account, I get access to everything under the purview of my credential.

Log into the Maya plugin, server checks that I have plugin access, plugin works. Same for standalone V3.X (which thankfully finally works properly)

I have had no less than 14 attempts at making the maya plugin activate in 2017, but no matter what credentials combo I use, it wont activate (I paste it into the main website, and magically it works, so the Maya plugin is truly broken in this regard)

Any help here would be greatly appreciated.

The username and password you need to enter to activate Octane is the same as you need to log in into:

https://account.otoy.com/

If you are already logged in but don't remember your password, you need to sign out:

https://account.otoy.com/sign_out

And then request a password reset link:

https://account.otoy.com/forgot_password

This will let you change your password.

Regarding the different account on the forums that's something that needs to be addressed, but still couldn't find the time to do so.

I hope that helps.

Is having a site login(for users)and a site admin login(for license and system manager) something that would be possible to work into your licensing system?

./rrb

rrbarb wrote:Is having a site login(for users)and a site admin login(for license and system manager) something that would be possible to work into your licensing system?

I am not sure I fully understand this, could you please expand your explanation and those roles?

Thank you Mojave, i was actually speaking about the maya plugin asking for a login credential that never works. Putting in my otoy credentials and the one listed on the license page both fail. The standalone version is working fine.

Thank you for chiming in

[Solved]
After ignoring the "Octane V2 Username" (which are numbers) and using my full email address instead (and not my Tenth_Old_Man handle)

AND

Using the Maya Plugin v2 password (not actual login credentials as Maya plugin confusingly states)

I am now able to use the Maya Plugin.

This problem seems to be lingering in the plugin or back-end db tables not being in sync, but hopefully no one else will have to suffer through this.

rrbarb wrote:
Is having a site login(for users)and a site admin login(for license and system manager) something that would be possible to work into your licensing system?


I am not sure I fully understand this, could you please expand your explanation and those roles?

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--Within a Company that uses Otoy Licenses there could be multiple locations[sites]. There is one account for the Company that licenses are purchased under and controlled by. This account has full privilege- download, unlock ect.
In order for multiple Users to access the licenses these credentials must be shared to multiple Users. Giving multiple Users full privilege--
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What I am asking for is the ability for this Company account owner to designate/add/delete/manage user accounts for the licenses and define the role for those accounts to either User or Admin.
Then each location could have an designated Admin who could control their site Users autonomously.


./rrb