Changes

This document describes the OpenLDAP directory data organisation for the [https://www.stoney cloud (Online) '''Backup -backup.com/ stoney backup] service'''.

The following chapters explain the data organisation of the stoney cloud OpenLDAP directory, in this case we looking at the (Online) '''Backup [https://www.stoney-backup.com/ stoney backup] service'''.

| style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>'''SelfcareSelf-Service'''</center>

| style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>'''SelfcareSelf-Service'''</center>

| style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>'''SelfcareSelf-Service'''</center>

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Can the selfcare Self-Service interface be used with the credentials of the backup account? Either <code>TRUE</code> (yes) or <code>FALSE</code> (no). Default is <code>FALSE</code> (no).

The sub tree stores the notification information for the (online) backup service for the reseller Reseller Ltd. with the uid 4000000. This information is used independently of the notification settings of the users. The idea is, that the reseller can receive notifications for a customer and reaction react on the received information (for example, when the quota has been reached):

| style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>'''SelfcareSelf-Service'''</center>

* sstVolumeCapacityDefault: 1 GigabyteGibibyte (GiB)* sstVolumeCapacityMin: 1 GigabyteGibibyte (GiB)* sstVolumeCapacityMax: 500 GigabytesGibibyte (GiB)* sstVolumeCapacityStep: 1 GigabyteGibibyte (GiB)

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>1 KilobyteKibibyte (KiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 1 x 10242¹⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 10241 024

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>1 MegabyteMebibyte (MiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 1 x 1024 x 10242²⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 10485761 048 576

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>1 GigabyteGibibyte (GiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 1 x 1024 x 1024 x 10242³⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 10737418241 073 741 824

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>5 GigabytesGibibyte (GiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 5 x 1024 x 1024 x 10242³⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 53687091205 368 709 120

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>10 GigabytesGibibyte (GiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 10 x 1024 x 1024 x 10242³⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 1073741824010 737 418 240

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>100 GigabytesGibibyte (GiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 100 x 1024 x 1024 x 10242³⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 107374182400107 374 182 400

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>500 GigabytesGibibyte (GiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 500 x 1024 x 1024 x 10242³⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 536870912000536 870 912 000

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>1 TerabyteTebibyte (TiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 2⁴⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 1 x 1024 x 1024 x 1024 x 1024099 511 627 776 |-| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>1 Pebibyte (PiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 10995116277762⁵⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 1 125 899 906 842 624 |-| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>1 Exbibyte (EiB)</center>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| 2⁶⁰| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| 1 152 921 504 606 846 976

| style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>'''SelfcareSelf-Service'''</center>

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>MAYMUST</center>

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstVolumeCapacityDefaultsstMailFrom

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The mail address, from which the credentials are sent from. For example: * <code>Support stepping stone GmbH <support@stepping-stone.ch></code>).If this attribute does not exist, the* <code>sstMailFrom</code>from* <code>ou=settings,uid=&lt;UID&gt;,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org</code>must be taken.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstVolumeCapacityMinsstMailTo

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| If this multi-valued attribute is set with one or mail address(es), then these recipients will receive the same information as the <code>login</code> user or the <code>owner</code>, depending on the value of <code>sstSendCredentialsTo</code> under <code>ou=settings,uid=&lt;UID&gt;,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org</code>. Normally, this attribute is not set for the credentials.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstVolumeCapacityStepsstMailTemplate

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"|* Arrow left / Arrow right: 1 Gigabyte The template, that is used to create the mail that is sent to either the user logged in (sstVolumeCapacityStep<code>sstSendCredentialsTo: login</code>)or to the owner of then newly created service (<code>sstSendCredentialsTo: owner</code>. For example:* Page up / Page down<code>sstTemplate: 10 Gigabyte (10 x sstVolumeCapacityStep)file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/credentials/credentials_mail</code>.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstNotificationWarningMediumChangesstMailTemplateFormatSource

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Can a user change The format of the notification warning medium? Either source template. Supported values:* <code>TRUEtxt</code>* <code>html</code>Place holder:* For both <code>txt</code> (yes) or <code>FALSEhtml</code> as a source and <code>txt</code> or <code>html</code>, the place holders have the form of <code>{$placeholder}</code> (no). The default is Default would normally be <code>FALSEtxt</code> (no).

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstNotificationWarningMediumAddsstMailTemplateFormatTarget

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Can a user add new notification warning mediums (<code>mobileTelephoneNumber</code> or <code>mail</code>? Either <code>TRUE</code> (yes) or <code>FALSE</code> (no)The format of the target. The default is Supported values:* <code>TRUEtxt</code> (yes). Currently, only adding new * <code>mailhtml</code> addresses are supported.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstQuotaChangesstTemplate

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Can The template, that is used to create the user change attachment that is sent with the quota? Either mail. For example:* <code>TRUE<sstTemplate: file:/code> (yes) or <code>FALSE//var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/credentials/credentials_attachment</code> (no). Default is FALSE (no).

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstSendCredentialsTosstTemplateFormatSource

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| To whom do we send The format of the access data or credentials. At least one entry must existsource template. Possible Supported values:* <code>sstSendCredentialsTo: logintxt</code>* <code>odt</code>Place holders: The access data * If we have <code>txt</code> or credentials are sent to <code>html</code> as a source and <code>txt</code> or <code>html</code>, the person logged inplace holders have the form of <code>{$placeholder}</code>.* If we have <code>sstSendCredentialsTo: ownerodt</code> as a source and <code>odt</code>: The access data or credentials are sent <code>pdf</code> as a target, then [https://github.com/IvanGuardado/PHP-Easy-Report PHP-Easy-Report] is used to replace the owner (person), placeholders. These have the service belongs toform of <code>&#123;&#123;placeholder&#125;&#125;</code>.<br />

|-| style="border-top:none;border-bottom:0The complete path and file name is a string concatenation of the values of the attributes <code>sstTemplate</code>, <code>preferredLanguage</code> and <code>sstTemplateFormatSource</code> (with a dot in between the values).002cm solid #000000;border-leftFor example:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstMailFrom| style="border-top* <code>sstTemplate:none;border-bottomfile:0///var/www/selfcare/htdocs/themes/selfcare.002cm solid #000000;border-left:0tombstone.002cm solid #000000;border-right:none;padding:0.097cm;"| ch/templates/services/backup/credentials/credentials_attachment<center/code>MAY* </centercode>| style="border-toppreferredLanguage:none;borderen-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| GB<center/code>x* <code>sstTemplateFormatSource: odt</centercode>| style="border-topThis gives us:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <centerbr />* </centercode>| style="border-topfile:none;border-bottom:0///var/www/selfcare/htdocs/themes/selfcare.002cm solid #000000;border-left:0tombstone.002cm solid #000000;borderch/templates/services/backup/credentials/credentials_attachment.en-right:none;padding:0GB.097cm;"| <center>ode</centercode>| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The mail address, from which the credentials are to Default would normally be sent from. In the example from above, this value is '''Support stepping stone GmbH <support@stepping-stone.chcode>odt</code>'''.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| preferredLanguagesstTemplateFormatTarget

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The notification language, which will be used to used in format of the mails, that are sent to the reseller, according to [httptarget. Supported values:* <code>txt</code>* <code>odt</www.ietf.orgcode>* <code>pdf</rfc/rfc1766.txt RFC 1766] code>Note to Self-Service developer(s). Please be aware of the following issues when using [httphttps://wwwgithub.iso.orgcom/isoIvanGuardado/english_country_names_and_code_elements ISO 3166PHP-1Easy-alphaReport PHP-2 code]Easy-[httpReport]://www* Minor: Spaces (and other special characters) in the document file names are going to be a problem since the names don't get escaped.loc.gov/standards/iso639* Major: You must provide a manually-2/php/code_list.php ISO 639created unique temp-1 Code]. For example '''dedirectory for the PHP-CH''' or '''enEasy-GB'''Report object, otherwise there will be race-conditions.Default would normally be <code>pdf</code>.

==== Backup Reseller Templates ====This sub tree contains the templates for the Credentials Place Holders E-Mail (onlinetxt/html) backup service for the reseller Reseller Ltd. with the uid 4000000: dn: ou=templates,uid=4000000,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org objectclassAddress with an example: top objectclass{$company} stepping stone GmbH {$salutation} {$name} {$surname} Mr. Michael Eichenberger {$address} Neufeldstrasse 9 {$country}-{$zip} {$location} CH-3013 Bern Date with an example: organizationalUnit ou{$day} 16 {$month} August {$year} 2013 Backup Service with an example: templates description{$uid} 4000124 {$password} XlWz4Qa# Optional Values: This sub tree contains the {$externalID} 12345 ====== Credentials Place Holders LibreOffice (odt) ======LibreOffice (odt) templates for have the same place holders as the E-Mail (onlinetext/html) backup service for templates. The only thing that changes, are the reseller Reseller Ltddefinitions. with Instead of <code>{$placeholder}</code> we have <code>&#123;&#123;placeholder&#125;&#125;</code>. ===== Backup Reseller Quota Templates =====Warns the uid 4000000user when the backup is running out of space (quota).

dn: ou=credentialsquota,ou=templates,uid=4000000,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org

ou: credentialsquota description: This leaf contains the credential quota templates for the (online) backup service.

sstMailTemplate: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/credentialsquota/credentials_mailquota_mail sstMailTemplateFormatSource: txt sstMailTemplateFormatTarget: txt sstMailTemplateReseller: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/quota/quota_mail_reseller

| style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>'''SelfcareSelf-Service'''</center>

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The mail address, from which the credentials quota mails are sent from. For example: * <code>Support stepping stone GmbH <support@stepping-stone.ch></cdoecode>).If this attribute does not exist, the * <code>sstMailFrom</code> from * <code>ou=settings,uid=<&lt;UID>&gt;,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org</code> must be taken.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| If this multi-valued attribute is set with one or mail address(es), then these recipients will receive the same information as the login user or the owner, depending on the value of <code>sstSendCredentialsTo</code> under <code>ou=settings,uid=<UID>,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org</code>. Normally, this attribute is not set.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The template, that is used to create the mail that is sent to either the user logged in (owner of the service if <code>sstSendCredentialsTosstBackupWarningOn: loginTRUE</code>) or to the owner of then newly created service (and <code>sstSendCredentialsTosstNotificationWarningMedium: ownermail</code>. If the <code>mail</code> is not set, you must look for the <code>mail</code> in the owners person entry under <code>uid=&lt;UID&gt;,ou=people,dc=stoney-cloud,dc=org</code>. For example:

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstTemplatesstMailTemplateReseller

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>x¹</center>

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The path and name to a templatefile, that is used to create inform one or more people if the attachment that multi-valued attribute <code>sstMailTo</code> is sent with set in the notifications sub tree of the reseller* <code>ou=notifications,uid=&lt;UID&gt;,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=organd if <code>sstNotificationWarning</code> is set to <code>quota</code>. In most cased, the attribute <code>sstMailTo</code> is set to the support organisations mailaddress. For example:* <code>sstMailTo: Support stepping stone GmbH &lt;support@stepping-stone.ch&gt></code>This way, the support organisation will be pre-informed for when the customer should call or write. The information the recipients will receive, is the same as the owner, but will formatted according to:* <code>sstTemplate: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/credentialsquota/credentials_attachmentquota_mail_reseller</code>* <code>sstMailTemplateResellerFormatSource: txt</code>* <code>sstMailTemplateResellerFormatTarget: txt</code>.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstTemplateFormatSourcesstMailTemplateResellerFormatSource

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>x¹</center>

* <code>odthtml</code>Place holdersholder:* If we have For both <code>txt</code> or <code>html</code> as a source and <code>txt</code> or <code>html</code>, the place holders have the form of <code>{$placeholder}</code>.* If we have <code>odt</code> as a source and <code>odt</code> or <code>pdf</code> as a target, then [https://github.com/IvanGuardado/PHP-Easy-Report PHP-Easy-Report] is used to replace the placeholders. These have the form of <code>&#123;&#123;placeholder&#125;&#125;</code>.<br />

* <code>sstTemplate: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/credentialsquota/credentials_attachmentquota_mail_reseller</code>

* <code>sstTemplateFormatSource: odttxt</code>

* <code>file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/credentialsquota/credentials_attachmentquota_mail_reseller.en-GB.txt</code>Default would normally normallb be <code>odttxt</code>.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| sstTemplateFormatTargetsstMailTemplateResellerFormatTarget

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>x¹</center>

* <code>odthtml</code>* <code>pdf</code>Note to selfcare developer(s). Please be aware of the following issues when using [https://github.com/IvanGuardado/PHP-Easy-Report PHP-Easy-Report]:* Minor: Spaces (and other special characters) in the document file names are going to be a problem since the names don't get escaped.* Major: You must provide a manually-created unique temp-directory for the PHP-Easy-Report object, otherwise there will be race-conditions.Default would normally normallb be <code>pdftxt</code>.

====== Credentials Quota Place Holders E-Mail (txt/html) ======Address with an An example: {$companysalutation} stepping stone GmbH Mr. {$salutation} {$name} {$surname} Mr. Michael Eichenberger {$addressuid} Neufeldstrasse 9 3723707 {$countrypercent}- 98 {$zipquota} 100 {$locationbackup_size} CH-3013 Bern40 {$snapshot_size} 48

Date with an exampleOptional Values: {$dayexternalID} 16 {$month} August {$year} 2013 12345

Backup Service with an example:====== Quota Place Holders LibreOffice (odt) ====== LibreOffice (odt) templates have the same place holders as the E-Mail (text/html) templates. The only thing that changes, are the definitions. Instead of <code>{$uidplaceholder} 4000124 {$password} XlWz4Qa</code> we have <code>&#123;&#123;placeholder&#125;&#125;</code>.

=====Backup Reseller Schedule Templates = Credentials ====Warns the user if the backup wasn't executed at the planned time (schedule). This sub tree contains the schedule templates for the (online) backup service: dn: ou=schedule,ou=templates,uid=4000000,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: sstTemplateSetup ou: schedule description: This leaf contains the schedule templates for the (online) backup service. sstMailFrom: Support stepping stone GmbH <support@stepping-stone.ch> sstMailTemplate: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/schedule/schedule_mail sstMailTemplateFormatSource: txt sstMailTemplateFormatTarget: txt sstMailTemplateReseller: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/schedule/schedule_mail_reseller sstMailTemplateFormatSource: txt sstMailTemplateFormatTarget: txt ====== Schedule Place Holders E-Mail (txt/html) ======An example: {$salutation} Mr. {$surname} Eichenberger {$scheduled_date} 01. August 2013 {$scheduled_time} 15:00 {$gecos} Michael Eichenberger {$computer} my-laptop {$last_success} The last successful backup was made on the 03. July 2013 at 14:45 {$uid} 1234567 Optional Values: {$externalID} 12345 ====== Schedule Place Holders LibreOffice (odt) ======

===== Backup Reseller Quota Unsuccessful Templates =====Informs the user if the backup was executed, but finished with errors (unsuccessful). This sub tree contains the quota unsuccessful templates for the (online) backup service: dn: ou=quotaunsuccessful,ou=templates,uid=4000000,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org

ou: quotaunsuccessful description: This leaf contains the quota schedule templates for the (online) backup service.

sstMailTo: Support stepping stone GmbH <support@stepping-stone.ch> sstMailTemplate: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/quotaunsuccessful/quota_mailunsuccessful_mail

sstMailTemplateReseller: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/quotaunsuccessful/quota_mail_resellerunsuccessful_mail_reseller

====== Unsuccessful Place Holders E-Mail (txt/html) ======An example: {$salutation} Mr. {$surname} Eichenberger {$scheduled_date} 01. August 2013 {$scheduled_time} 15:00 {$gecos} Michael Eichenberger {$computer} my-laptop {$last_success} The last successful backup was made on the 03. July 2013 at 14:45 {$uid} 1234567 Optional Values: {$externalID} 12345 Example template: <pre>Subject: Online Backup information for account {$uid} {$salutation} {$surname} Your backup for the account '{$gecos}' and the computer '{$computer}', scheduled for the {$scheduled_date} at {$scheduled_time}, was not successful.{$last_success} If the problem can be solved with a manual Backup, you may ignore this message. Otherwise please contact us under: support@stepping-stone.ch Kind regardsyour stepping stone GmbH support team --stepping stone GmbHNeufeldstrasse 9CH-3012 Bern Telefon: +41 31 332 53 63www.stepping-stone.chsupport@stepping-stone.ch</pre> Which results in the following mail for the backup account 4000152:<pre> Dear Mr. Kläy Your backup for the account 'Pat Klaey' and the computer 'pat-GT60', scheduled for the 18. Aug 2013 at 17:15, was not successful.The last successful backup was made the 01. July 2013 at 12:00 If the problem can be solved with a manual Backup, you may ignore this message. Otherwise please contact us under: support@stepping-stone.ch Kind regardsyour stepping stone GmbH support team --stepping stone GmbHNeufeldstrasse 9CH-3012 Bern Telefon: +41 31 332 53 63www.stepping-stone.chsupport@stepping-stone.ch</pre> ====== Unsuccessful Place Holders LibreOffice (odt) ======LibreOffice (odt) templates have the same place holders as the E-Mail (text/html) templates. The only thing that changes, are the definitions. Instead of <code>{$placeholder}</code> we have <code>&#123;&#123;placeholder&#125;&#125;</code>. ===== Backup Reseller Schedule Upgrade Templates =====If the Backup Client is too old, inform the user (upgrade). This sub tree contains the schedule '''upgrade''' templates for the (online) backup service: dn: ou=scheduleupgrade,ou=templates,uid=4000000,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org

ou: scheduleupgrade description: This sub tree leaf contains the schedule templates for the (online) backup service. The leaf contains the information about the sender and default recipient of the mails sent.

sstMailTosstMailTemplate: Support stepping stone GmbH <support@stepping-stonefile:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch>/templates/services/backup/upgrade/upgrade_mail sstMailTemplateFormatSource: txt sstMailTemplateFormatTarget: txt sstMailTemplateReseller: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/upgrade/upgrade_mail_reseller sstMailTemplateFormatSource: txt sstMailTemplateFormatTarget: txt

====== Upgrade Place Holders E-Mail (txt/html) ======An example: {$salutation} Mr. {$surname} Eichenberger {$scheduled_date} 01. August 2013 {$scheduled_time} 15:00 {$gecos} Michael Eichenberger {$computer} my-laptop {$last_success} The last successful backup was made on the 03. July 2013 at 14:45 {$uid} 1234567 Optional Values: {$externalID} 12345 Example template: <pre>Subject: Online Backup information for account {$uid} {$salutation} {$surname} Your backup for the account '{$gecos}' and the computer '{$computer}', scheduled for the {$scheduled_date} at {$scheduled_time}, was not successful.{$last_success} If the problem can be solved with a manual Backup, you may ignore this message. Otherwise please contact us under: support@stepping-stone.ch Kind regardsyour stepping stone GmbH support team --stepping stone GmbHNeufeldstrasse 9CH-3012 Bern Telefon: +41 31 332 53 63www.stepping-stone.chsupport@stepping-stone.ch</pre> Which results in the following mail for the backup account 4000152:<pre> Dear Mr. Kläy Your backup for the account 'Pat Klaey' and the computer 'pat-GT60', scheduled for the 18. Aug 2013 at 17:15, was not successful.The last successful backup was made the 01. July 2013 at 12:00 If the problem can be solved with a manual Backup, you may ignore this message. Otherwise please contact us under: support@stepping-stone.ch Kind regardsyour stepping stone GmbH support team --stepping stone GmbHNeufeldstrasse 9CH-3012 Bern Telefon: +41 31 332 53 63www.stepping-stone.chsupport@stepping-stone.ch</pre> ====== Upgrade Place Holders LibreOffice (odt) ======LibreOffice (odt) templates have the same place holders as the E-Mail (text/html) templates. The only thing that changes, are the definitions. Instead of <code>{$placeholder}</code> we have <code>&#123;&#123;placeholder&#125;&#125;</code>. ===== Backup Reseller Unsuccessful No Backup Templates =====Tell the user, that they have a backup account, but it was never used (no backup). This sub tree contains the unsuccessful '''no backup''' templates for the (online) backup service: dn: ou=unsuccessfulno backup,ou=templates,uid=4000000,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org

ou: unsuccessfulno backup description: This sub tree leaf contains the schedule templates for the (online) backup service. The leaf contains the information about the sender and default recipient of the mails sent.

sstMailTosstMailTemplate: Support file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/no backup/no backup_mail sstMailTemplateFormatSource: txt sstMailTemplateFormatTarget: txt sstMailTemplateReseller: file:///var/www/selfcare/htdocs/themes/selfcare.tombstone.ch/templates/services/backup/no backup/no backup_mail_reseller sstMailTemplateFormatSource: txt sstMailTemplateFormatTarget: txt ====== No Backup Place Holders E-Mail (txt/html) ======An example: {$salutation} Mr. {$surname} Eichenberger {$scheduled_date} 01. August 2013 {$scheduled_time} 15:00 {$gecos} Michael Eichenberger {$computer} my-laptop {$last_success} The last successful backup was made on the 03. July 2013 at 14:45 {$uid} 1234567 Optional Values: {$externalID} 12345 Example template: <pre>Subject: Online Backup information for account {$uid} {$salutation} {$surname} Your backup for the account '{$gecos}' and the computer '{$computer}', scheduled for the {$scheduled_date} at {$scheduled_time}, was not successful.{$last_success} If the problem can be solved with a manual Backup, you may ignore this message. Otherwise please contact us under: support@stepping-stone.ch Kind regardsyour stepping stone GmbH support team --stepping stone GmbHNeufeldstrasse 9CH-3012 Bern Telefon: +41 31 332 53 63www.stepping-stone.chsupport@stepping-stone.ch</pre> Which results in the following mail for the backup account 4000152:<pre> Dear Mr. Kläy Your backup for the account 'Pat Klaey' and the computer 'pat-GT60', scheduled for the 18. Aug 2013 at 17:15, was not successful.The last successful backup was made the 01. July 2013 at 12:00 If the problem can be solved with a manual Backup, you may ignore this message. Otherwise please contact us under: support@stepping-stone.ch Kind regardsyour stepping stone GmbH support team --stepping stone GmbHNeufeldstrasse 9CH-3012 Bern Telefon: +41 31 332 53 63www.stepping-stone.chsupport@stepping-stone.ch</pre> ====== No Backup Place Holders LibreOffice (odt) ======LibreOffice (odt) templates have the same place holders as the E-Mail (text/html) templates. The only thing that changes, are the definitions. Instead of <code>{$placeholder}</code> we have <code>&#123;&#123;placeholder&#125;&#125;</code>.

dn: ou=accounts,ou=backup,ou=services,dc=fossstoney-cloud,dc=org

<source lang="ldif">dn: uid=3723707,ou=accounts,ou=backup,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: account objectclass: posixAccount objectclass: shadowAccount objectclass: sstBackup objectclass: sstProvisioning objectclass: sstRelationship uid: 3723707 userPassword: {SSHA}E/KLUgeAtApAPQ7mG2GMddCxTE9m9QOS uidNumber: 3723707 gidNumber: 3723707 cn: Michael Eichenberger gecos: Michael Eichenberger homeDirectory: /var/backup/7/707/723/3723707/chroot/./home/3723707 loginShell: /bin/sh shadowLastChange: 11108 shadowMax: 99999 shadowWarning: 7 shadowFlag: 134539460 sstBackupIntervalHourly: 0 sstBackupIntervalDaily: 7 sstBackupIntervalWeekly: 4 sstBackupIntervalMonthly: 3 sstBackupIntervalYearly: 0 sstBackupIterations: 99sstBackupWarningDays: 1 sstBackupWarningNumbers: 0 sstBackupWarningOn: TRUE sstNotificationWarningLevel: 85 preferredLanguage: de-CH sstNotificationWarningMedium: mail sstUseSelfcare: FALSE sstUseSSH: TRUE sstIsActive: TRUE sstQuota: 10737418240 sstBackupSize: 0 sstIncrementSize: 0 sstBackupLastSuccessfulBackup: computer:20130923T063554Zhost: sst-int-054sstProvisioningMode: add sstProvisioningExecutionDate: 0 sstProvisioningState: 0 sstBelongsToResellerUID: 4000000 sstBelongsToCustomerUID: 4000001 sstBelongsToPersonUID: 4000002sstBelongsToServiceUID: 4000003</source>

| style="border-top:0.002cm solid #000000;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center>'''SelfcareSelf-Service'''</center>

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The unique identifier (uid). This attribute is created by the selfcare Self-Service interface by reading (and incrementing) the next free uid from "cn=nextfreeuid,ou=administration,dc=stoney-cloud,dc=org".

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Identifies the entry's password and encryption method in the following format: <code>{encryption method}encrypted password</code>. For example: {SSHA}zBiT1dHAZh/8zbCeyocRVWhdP0j9xJ3U. This password will be automatically set through the selfcare Self-Service interface. Afterwords, the password can be changed by the user (including the reseller and customer).

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Named for historical reasons, the GECOS field is mandatory and is used to store extra information (such as the user's full name). Utilities such as finger or getent access this field to provide additional user information. For a personal account, this entry would consist of <code>givenName</code> and <code>surname</code>, for example <code>Michael Eichenberger</code>. These values are taken from the owners entry (ou=people). For a service account, the attribute <code>sstDisplayName</code> from the corresponding service would be used for the content of this attribute. Please be aware, that this attribute is a '''IA5String''' (OID=1.3.6.1.4.1.1466.115.121.1.26) IA5 (almost ASCII) character set (7-bit). Does NOT allow extended characters e.g. é, Ø, å etc. The selfcare Self-Service interface automatically creates the content of this attribute. The user (including the reseller and customer) can modify this attribute as desired (except for the IA5 restrictions).

<code>/var/backup/g/efg/bcd/abcdefg/chroot/./home/abcdefg</code><br/><code>/var/backup/7/707/723/3723707/chroot/./home/3723707</code> This attribute is created by the selfcare Self-Service interface.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Related to the /etc/shadow file, this attribute specifies number of days between January 1, 1970, and the date that the password was last modified. Must be set to the day, that the password was set (must be updated, when the password is changed). This attribute is created by the selfcare Self-Service interface.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Related to the /etc/shadow file, this attribute specifies the maximum number of days the password is valid. The default is '''99999''', which corresponds to about 273 years. In reality, this means, that the user does not need to change the password. This attribute is created by the selfcare Self-Service interface. The value is taken from the "ou=settings,uid=<UID>,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org" entry.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Multi-valued attribute with the E-Mail addresse(s) that is used for the notification of the user(s), if the attribute <code>sstBackupWarningOn</code> ist <code>TRUE</code> and the attribute <code>sstNotificationWarningMedium</code> ist set to <code>mail</code>. If <code>sstNotificationWarningMediumAdd</code> is set to <code>TRUE</code> and the backup service belongs to a personal account, the <code>mail</code> entry would be taken from the owners entry (ou=people). For a backup service belonging to another serviĉe, the selfcare Self-Service would ask the user for the <code>mail</code> address.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Can the selfcare Self-Service interface be used with the credentials of the backup account? Either <code>TRUE</code> (yes) or <code>FALSE</code> (no). Default is <code>FALSE</code> (no) and is taken from the "ou=defaults,uid=<UID>,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org" entry.

| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| Stores the service UID (Unique Identifier) of the service the leaf belongs to. This UID can be used to look up other information. For a customer mail account, the service the account belongs to will most likely be a stoney cloud [[stoney_cloud:_OpenLDAP_directory_data_organisation#Units_.28instances.29 | unit]] (instance).

* '''x³''': Either <code>sstBelongsToPersonUID</code> or <code>sstBelongsToServiceUID</code> must bei set. The attribute <code>sstBelongsToServiceUID</code> must be set for all the stoney cloud [[stoney_cloud:_OpenLDAP_directory_data_organisation#Units_.28instances.29 | units]] (instances).

dn: ou=groups,ou=backup,ou=services,dc=fossstoney-cloud,dc=org

dn: cn=3723707,ou=groups,ou=backup,ou=services,dc=fossstoney-cloud,dc=org

* Entscheid chroot-Umgebung. TMU/CAF/PKL/MEI** chroot-Umgebung mit einer Kombination von busybox, Jailkit und dem täglich ablaufendem Backup-Script (als aufrufende Instanz)** rsync vom Host (als static Binary)** busybox vom Host (als static Binary) * Verzicht auf Bind-Mount (.snapshots ist read only) -> CAF* LDAP Struktur -> MEI/TMU* Neuer Backup Server aufbauen (Gleicher Fingerprint) -> TMU/MEI* Backup Script (prov-backup-rsnapshot) -> PKL* SSHA Umstellung bei den Passwörtern -> MEI/CWI * Icons: http://www.famfamfam.com/lab/icons/silk/ == Backup Provisioning ==Die Provisionierung benötigt die drei Attribute '''sstProvisioningMode''' und '''sstProvisioningState''' und '''sstProvisioningExecutionDate'''. Ablauf:# '''sstProvisioningMode''': Die Applikation '''Selfcare''' beschreibt das Attribut '''sstProvisioningMode''' mit den Werten '''add''', '''modify''' der '''delete'''.## '''sstProvisioningMode: add''': Der Service soll hinzugefügt werden. Dieser Fall muss mehrmals nacheinander aufgerufen werden können. Beispiel: Bei Online Backup wurde die chroot-Umgebung bereits erstellt, dann müsste ein '''add''' nur noch kontrollieren, ob die chroot-Umgebung aktuell ist, falls nicht, müssten die entsprechenden Punkte aktualisiert werden.## '''sstProvisioningMode: modify''': Der Service soll modifiziert werden.## '''sstProvisioningMode: delete''': Der Service soll gelöscht werden.# '''sstProvisioningExecutionDate''': Die Applikation '''Selfcare''' beschreibt das Attribut '''sstProvisioningExecutionDate''' mit dem gewünschten Ausführungszeitpunkt. Zwei Fälle:## '''0''': Dies bedeutet "sofort" und wird durch den Provisionierungs-Daemon '''provisioning.pl''' ausgewertet.## '''See the [YYYY][MM][DD]'''stoney core: Das gewünschte Ausführungsdatum ([http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]). Muss mindestens ein Tag später als das aktuelle Datum sein, da diese Attribut durch ein alle 24 Stunden aufgerufenes Aufräum-Script gelesen wird. Der genaue Ausführungszeitpunkt kann somit nicht bestimmt werden (da abhängig vom Ausführungszeitpuntk der Aufräum-Scripts und der Anzahl anstehenden Aufgaben).# '''sstProvisioningState''': Die Applikation '''Selfcare''' oder der Provisionierungs-Daemon '''OpenLDAP provisioning|OpenLDAP provisioning.pl''' beschreiben das Attribut '''sstProvisioningState''':## '''Keine Provisionierung nötig''': Falls eine Änderung keine Provisionierung im Backend verlangt (zum Beispiel bei einer Passwört-Änderung), wird das Attribut '''sstProvisioningState''' direkt durch die Applikation '''Selfcare''' it dem aktuellen Datum und der aktuellen Zeit in Form von '''[YYYY][MM]page for the overview of the provisioning functionality and [DD]T[hh][mm][ss]''' ausfüllen ([httpstoney backup://en.wikipedia.org/wiki/ISO_8601 ISO 8601]) beschrieben. In diesem Falle ignoriert der Provisionierungsprov-Daemon '''provisioning.pl''' die Modifikation.## Provisionierung nötig: Falls eine Änderung eine Provisionierung im Backend verlangt (zum Beispiel bei einer Quotabackup-Änderung), muss die Applikation '''Selfcare''' dieses Attribut auf den Wert '''0''' setzen. Nach der erfolgreichen Provisionierung muss Provisionierungs-Daemon '''provisioning.pl''' das Attribut '''sstProvisioningState''' mit dem aktuellen Datum und der aktuellen Zeit in Form von '''[YYYYrsnapshot][MM][DD]T[hh][mm][ss]''' ausfüllen ([http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]).  Die Applikation '''Selfcare''' darf erst dann wieder eine Modifikation durch einen Benutzer zulassen, wenn das Attribut '''sstProvisioningState''' einen gültigen Zeitstempel in der Form von '''[YYYY][MM][DD]T[hh][mm][ss]''' ([http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]) hat. Technisch gesehen muss der Provisionierungs-Daemon '''the actual backup provisioning.pl''' im RefreshAndPersist Modus nur noch auf die LDAP-Mechanismen '''add''' und '''modify''' hören. Der LDAP-Mechanismus '''delete''' muss ignoriert werden.

[[Category:OpenLDAP directorystoney backup]][[Category:ServicesOpenLDAP directory]]