Skip to main content

Ceridian Dayforce (Legacy)

Connector name

agtdayforce

Connector type

Executable

Type (UI field value)

Ceridian Dayforce (Legacy)

Connector status / support

Customer-Verified

Clients may contact Bravura Security support for assistance with this connector. Troubleshooting and testing must be completed in the client's test environment as Bravura Security does not maintain internal test environments for the associated target system.

Upgrade notes

The agtdayforce.con connector that makes use of agtpython.exe and a Python script should be used instead of the legacy agtdayforce.exe connector. The legacy agtdayforce.exe connector, added in Connector Pack 4.4.0, was only able to list a limited set of attributes.

The new agtdayforce.con Python connector offers more flexibility and is able to list attributes by their json path and therefore be able to list more attributes from Dayforce.

The following Bravura Security Fabric operations are supported by Ceridian Dayforce (Legacy) connector:

  • list account attributes

  • List:

    • accounts

    • attributes

  • create account

  • update attributes

  • persistent listing

For a full list and explanation of each connector operation, see connector operations.

Preparation

Before you can target Ceridian Dayforce, you must set up a target administrator, and create a template account if Bravura Identity "create account" operations are to be supported.

Set up a target administrator

Ensure that a user account has been created within Ceridian Dayforce that is an administrative user and has access to manage Dayforce users.

Create a template account

Bravura Security Fabric uses template accounts as models or "blueprints" for creating new accounts in Ceridian Dayforce.

Ensure that a user account has been created within Ceridian Dayforce that will be used for the template account.

Targeting the Ceridian Dayforce system

For each Ceridian Dayforce system, add a target system in Bravura Security Fabric (Manage the System > Resources > Target systems):

  • Type is Ceridian Dayforce (Legacy)

  • Address uses options described in the table below:

Options marked with a redstar.png are required.

Option

Description

Server: redstar.png

The domain name URL for the Dayforce server. Default is www.dayforcehcm.com.

(key: server)

Port:

Port for the Dayforce server. Default is 443.

(key: port)

Connection over SSL:

Select to enforce SSL connections. Default is "true".

(key: ssl)

Validate the server's certificate when connecting:

Determines whether to validate the server’s security certificate for SSL connections. Default is "true".

(key: checkCert)

HTTP Network Proxy:

Specifies a network proxy URL to use for connecting.

(key: proxy)

Client ID: redstar.png

The Client ID on the Dayforce server that will be used to target.

(key: client)

Connector Listener Host:

The URL address that is used to start a web service to listen on and receive information for persistent listing for Ceridian Dayforce.

(key: servicehost)

Connector Listener Port:

The port that is used by the URL for the Connector Listener Host for peristent listing. Default is 5050.

(key: serviceport)

The full list of target parameters is explained in Target System Options .

Persistent listing

Persistent listing is supported by Ceridian Dayforce, which provides a special way to send back the user and attribute information.

The Ceridian Dayforce server will need to be configured for a notification service point that will be used by the agtdayforce connector for persistent listening. This notification service point is used for the Connector Listener Host and Connector Listener Port target system address parameters.

The connector will start a web service at an address such as http://<servicehost>:<port> where it listens and receives the information using the Connector Listener Host and Connector Listener Port target system address parameters. The Connector Listener Host is the URL address that will be used to access the web service.

Once the Ceridian Dayforce server has a corresponding notification, it will send the message over to the configured host and port, which will communicate back to the agtdayforce connector to parse the notification and record the relevant information back to the Bravura Security Fabric server.

Handling account attributes

You can view the complete list of attributes that Bravura Security Fabric can manage, including native and pseudo-attributes, using the Manage the system (PSA) module. To do this, select Ceridian Dayforce (Legacy) from the Manage the system > Resources > Account attributes > Target system type menu.

For information about the native Ceridian Dayforce attributes managed by Bravura Security Fabric , consult your Ceridian Dayforce documentation.

In this section: