Are you saying your cron task had these parameters already, has the exact same parameter values, and new users (not existing) are being pushed in with local authentication? I have never seen that. When these aren't provided it uses the upgrade method to determine but otherwise should use this. It is case sensitive so make sure you have the values all lowercase.
I'd say you could open a support ticket with IBM but 8.7 has hit end of mainstream support so you may not get a response if you haven't purchased extended support.
------------------------------
Steven Shull
Naviam
------------------------------
Original Message:
Sent: 06-03-2026 11:51
From: Chidambar Shastry
Subject: User Sync Authentication type issue from Manage to Suite with Rest API
Hi Steve,
I tried by setting parameter values against MASUSERSYNC cron as in above screenshot, but still am having the same issue.
------------------------------
Chidambar Shastry
Xyz
------------------------------
Original Message:
Sent: 06-02-2026 08:44
From: Steven Shull
Subject: User Sync Authentication type issue from Manage to Suite with Rest API
The MASUSERSYNC cron task was enhanced with new parameters for tracking the owner & authentication method (issuer) but I don't remember what version exactly that was done in. If you don't see the cron task parameters for it, try to delete and recreate the cron task instance to see if it adds the new parameters. Cron task parameters are defined on creation of the cron task which is why recreating it can show the additional parameters.
Owner must be local or scim (all lowercase) and you want it to be local. SCIM means the user comes from LDAP sync or the SCIM sync process in newer versions. This drastically limits what you can modify on the user record since you're telling it that the integration manages the user account.
Issuer in your case would be saml. Your identity provider will be labeled as default-saml but this feature is looking for local, ldap, or saml only and will use the appropriate one based on that. It won't matter on your version, but in 9.0 MAS was enhanced to support multiple identity providers of the same type (IE two different SAML providers like Okta & Entra). For customers on 9.0, it can only send users to the default-saml. 9.1 and the upcoming 9.2 user management is entirely different.

------------------------------
Steven Shull
Naviam
------------------------------