#Simplefile support how to#

Go to Filter and Sort if you want to filter for any specific Candidates.

Enter the integration name and select Configure Fields tab.

You must use the navigation properties to access any attachment.

PLEASE NOTE: To be compliant with data privacy laws, you cannot use attachment or photo as the starting entity.

Let us consider an example of selecting the Starting entity as Candidate and fetching the resume.

When you select Create button, you are directed to the Integration Center - Create a New Scheduled ATTACHMENT File Output Integration page.

From the Choose Integration Type page, select the following:.

From the Integration Center > My Integrations page, choose + Create More Integration Types.

From Integration Center landing Page, select My Integrations.

Go to Admin Center > Integration Center.

Procedure outlined in the Integration Center Guide:

i.e. each output record comes in the form of an attachment and requires individual / unique filename.

The 'Calculated File Name' functionality was introduced primarily for Attachment output.

The File Folder' is a required field and is used to define the destination of the output file.

For the 'File Extension' option, we can define the file extension / format the output file should use (.csv.

The date time suffix can be implemented down to the millisecond level (this will suffice for most integrations).

Using simple filenames, we can append date and datetime suffix, to uniquely identify files based upon each execution.

Simple File naming conventions can be used for most integrations.

Now restart the Access Server service with 'service openvpnas restart' and things should be operating correctly again.In the 'Destination Settings' section of Integration Center: The only thing you were missing for this to work was the ca.key file, which with the above commands should be regenerated fine. If it sees those do not have a CN that matches the current hostname setting in Access Server, it will regenerate those automatically for you. Whenever Access Server starts up, and it has no SSL certificates in its configuration database, it will use the fallback certificates. You can replace 'openvpnas' with a FQDN name of your server, but it's not really relevant. etc/web-ssl -type server -remove_csr -sn_off -serial 1 -name server -cn 'openvpnas' etc/web-ssl -type ca -unique -cn 'OpenVPN Web CA' Once you've done that, run these commands: Now to restore the fallback certificates to normal, I recommend you first backup the files in web-ssl. sacli -key 'cs.ca_bundle' -value_file './etc/web-ssl/ca.crt' ConfigPut sacli -key 'cs.cert' -value_file './etc/web-ssl/server.crt' ConfigPut sacli -key 'cs.priv_key' -value_file './etc/web-ssl/server.key' ConfigPut This will load those files into the Access Server configuration database, and the web services should use those the next time Access Server tries to start up. Now with that backed up, I suggest you run these following commands to load your signed certificates into the Access Server database.

#Simplefile support how to#

This guide shows how to backup the configuration of Access Server: To solve this properly there are 3 steps that you should do.Ģ: Load these certificates into the Access Server configuration database.ģ: Regenerate the self-signed certificates for Access Server.īefore you do anything though, make a backup. They're just in the wrong place, basically. So they shouldn't be regenerated anyways. I am making the assumption that the files now in the web-ssl directory are signed certificate, because you have TERENA SSL CA 3 in there, which is likely a valid party for providing signed certificates. But it is unable to do its programmed actions to ensure those certs are updated to current security standards for self-signed certificates. Apparently you don't have any web certs in your configuration database so Access Server thinks it has no valid certificates, so it goes to the fallback, and that one happens to now be your signed certificates. Most likely what happened is that you removed these files at some point and then instead put your own validated signed certificates in this directory. However in your case that fails and Access Server stops because the CA key is missing.įor some reason your ca.key file was deleted. It also as of version 2.9 will try to regenerate these automatically to meet stricter requirements. This is done so that Access Server has a fallback in case there are no valid certificates in Access Server's configuration database. The root cause is the valid signed certificates being loaded into the Access Server's SSL web certs fallback directory.Īccess Server maintains a CA and server web certificate in the web-ssl directory.