@syko24 said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@scottalanmiller said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@syko24 said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@scottalanmiller said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@wrx7m said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@tim_g said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@wrx7m said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@scottalanmiller said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
@dashrender said in Implement new Active Directory across Azure, on-prem, offsite, and cell-data IoT devices:
I'm with the rest - What are you trying to accomplish with AD? Can it be accomplished with other means?
I agree, if it were me, I'd not look at AD here at all. This is where Salt or Ansible seems like a better fit.
Can salt and/or ansible be used for user/device authentication?
Salt/Ansible is not an authentication platform. It's a systems management or state configuration system.
You can use Salt/Ansible to sync accounts across devices... so that you can control what local users and passwords are on which systems.
I didn't think it was, but did not know about the account sync functionality. Thanks for the info.
That's a key feature in SodiumSuite's design. Account management across platforms.
Is that available in SodiumSuite at this time?
Not quite, but VERY soon.
Every time I login to my account I always click on the Terminal tab hoping there will be some added functionality. Really looking forward to some of the more advanced features of the platform to be implemented.
LOL, honestly I do that from time to time, too. It was actually there at one point, but wasn't tested enough and we made the devs claw it back. That's why the tab is there, because it's working in testing.