Mitel Forums - The Unofficial Source

Mitel Forums => Mitel Software Applications => Topic started by: fishhead64 on August 29, 2025, 02:17:00 PM

Title: MICC Ignite SSO
Post by: fishhead64 on August 29, 2025, 02:17:00 PM

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

Thanks!
Al

Title: Re: MICC Ignite SSO
Post by: bajangerry on August 29, 2025, 02:37:45 PM

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

Title: Re: MICC Ignite SSO
Post by: fishhead64 on September 05, 2025, 09:18:29 AM

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?

Title: Re: MICC Ignite SSO
Post by: Tech Electronics on September 05, 2025, 11:08:09 AM

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

Title: Re: MICC Ignite SSO
Post by: fishhead64 on September 05, 2025, 12:50:27 PM

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?

Title: Re: MICC Ignite SSO
Post by: Tech Electronics on September 05, 2025, 05:14:10 PM

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

Title: Re: MICC Ignite SSO
Post by: Dogbreath on September 15, 2025, 11:50:00 AM

Bear in mind that MiCC licensing allows you to run a lab instance of the server as well.

Title: Re: MICC Ignite SSO
Post by: ACDeezNutz on September 21, 2025, 08:45:35 PM

You just need to rerun the MiCC setup and turn on Windows Authentication and then set up the AD sync from YSE.  No need to reinstall.  You do not AD on MiCollab as mentioned earlier.  They don't share login information.  You will just need to update the user account to have the MiCC user accounts match AD if they don't already then sync with AD to get it to start working.

Title: Re: MICC Ignite SSO
Post by: fishhead64 on September 24, 2025, 12:14:41 PM

thanks for the responses.

Title: Re: MICC Ignite SSO
Post by: billbry66 on December 27, 2025, 07:44:51 PM

sso for MICC refers to using cloudlink authentication not AD authentication
you would need to have a cloudlink account and link the customers cloudlink to their azure

Then you can run the setup wizard and change the authentication type to cloudlink ( micc must be above a certain version to support it)

NOTE : any change to authentication requires that all client access ( including YSE ) uses the new authentication methid

you cant have any locally authenticated accounts once the server has been changed

Title: Re: MICC Ignite SSO
Post by: kokolino23 on December 28, 2025, 04:56:44 PM

Quote from: billbry66 on December 27, 2025, 07:44:51 PM

sso for MICC refers to using cloudlink authentication not AD authentication
you would need to have a cloudlink account and link the customers cloudlink to their azure

Then you can run the setup wizard and change the authentication type to cloudlink ( micc must be above a certain version to support it)

NOTE : any change to authentication requires that all client access ( including YSE ) uses the new authentication methid

you cant have any locally authenticated accounts once the server has been changed

You're spot on with this! I agree with your statement

Sent from my Pixel 8 Pro using Tapatalk

Title: Re: MICC Ignite SSO
Post by: kokolino23 on December 28, 2025, 04:58:51 PM

Once you enable cloudlink, you'll have to run the setup wizard again if you need to disable it.

Sent from my Pixel 8 Pro using Tapatalk

Title: Re: MICC Ignite SSO
Post by: ACDeezNutz on December 29, 2025, 10:22:42 PM

MiCC YSE, Ignite, & CCMWeb supported methods:

1. Local login
2. Local AD Integration
3. CloudLink integration
4. CloudLink to Azure AD
5. CloudLink with 3rd party to Azure AD integration

You can do pretty much what ever you can think of.  It just depends on what works best for your site.  There might be even more methods supported but these are the main ones I've encountered.