Automic SaaS Diaries (Ep. 11-15): LDAP, APIs, Admins & More

Episode 11: LDAP & SSO in Automic SaaS

Managing user passwords can become tedious – especially for larger teams. Automic SaaS offers two convenient ways to simplify authentication:
SAML-based Single Sign-On (SSO) is supported natively and can be configured quickly in the AWI interface.
LDAP is also supported, but only in the secure LDAPS format. Your directory must be reachable via the Internet (e.g. Azure AD), and some setup assistance from Broadcom may be required.

Important to note: Kerberos authentication is not supported, as it doesn’t work in the AAKE environment.

Episode 12: Which APIs Work with Automic SaaS?

REST, JavaAPI, or CallAPI? Let’s clarify:
CallAPI is not compatible with Automic SaaS, since it relies on communication processors (CPs) – which no longer exist in this architecture.

The good news: You can use the /scripts REST API endpoint as a flexible and powerful replacement.
You can also use JavaAPI, as long as your library supports TLS version 21 or higher.

But the real future lies in the REST API. Most new features in Automic SaaS are built with REST in mind – making it the clear go-to interface for automation and integration.

Episode 13: Do We Still Need Admins in Automic SaaS?

Spoiler: Yes, absolutely.
Automic SaaS takes care of many operational tasks that used to require manual effort – like patching, system upgrades, and core monitoring. That’s great news! But Automic Admins are still essential.

They handle things like:

• Creating and managing clients
• Setting up users and roles
• Installing and troubleshooting agents
• Maintaining complex permission matrices (yes, that one!)

In other words: Less maintenance, more impact. Admins now focus on strategic improvements, internal automation projects, and helping teams get more out of Automic.

Episode 14: Creating Clients in Automic SaaS

Need more than just Client 100? You can create clients yourself – just like in an on-prem setup. Using the administration perspective in Client 0, you can:

• Add a new client
• Create or move users
• Import objects using transport case, REST JSON import, or XML

There are two differences compared to on-prem:

• Reorgs are handled automatically by Broadcom – no need to set them up yourself.
• If you want to duplicate an entire client, you’ll need help from the SaaS team, as the client copy utility is not available to end users.

Episode 15: Sending Emails from Automic SaaS

Notifications are a core part of automation. In Automic SaaS, you can still use both methods:

• Notification objects
• SEND_MAIL script function

SMTP settings can be fully configured by yourself, as you have access to all necessary objects in Client 0.

However, one migration challenge to keep in mind: Many corporate mail servers do not accept external SMTPS connections. If that’s the case, consider two alternatives:

• Set up a cloud-based email relay service for your SaaS system
• Use an Automic Agent installed inside your network as a mail gateway