MICC Ignite SSO

[fishhead64]

Can someone point me to the document that explains where and how to set up SSO for MICC, specifically Ignite?

Thanks!
Al

[bajangerry]

Are you referring to Active Directory integration? This is in the Installation and Administration Guide

[fishhead64]

Thanks, we're being told we can't just turn it on, we'll have to rebuild the servers from scratch? Could this possibly be true?

[Tech Electronics]

fishhead64,

This is totally possible as Mitel is looking for information is specific fields and formats.

If you look in your MiCollab: Configuration > Integrated Directory Service you will see the default mappings they are expecting.

Thanks,

TE

[fishhead64]

Default Attribute Mappings: Login is mapped to samaccountname which should be exactly what we want, yes?

We're talking about Ignite, which is in MiCC servers, and different than MiCollab, or does that push through from AD/Azure=>MiCollab=>MiCC & MIR?

[Tech Electronics]

fishhead64,

No it doesn't push anything through as that would defeat the point of AD.

I have never seen it used on just one product and not the other so I doubt it will go without a hitch if it isn't setup that way.

What I have seen during the installation process of the MiCC is that you can use Basic Authentication or Windows Authentication.

Basic Authentication uses what is programmed in the Users Profile.

Windows Authentication uses what is configured in your Windows AD.

Setting it up after the fact can be done, but I haven't done it without configuring it for MiCollab as well.

As for what could go wrong if you don't, I am not sure, but my best guess is that since it has to match employees to what is configured in the MiCC which gets its information from the MiVB which gets its information from the MiCollab there could be issues.

I think I have a best practice document from Mitel on this, but it is a pdf and I can't post those here. This is usually where you will want to get your Mitel VAR involved to help with setting this up.

Thanks,

TE