Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:software:tim:encryption_tim
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:software:tim:encryption_tim [2018/06/25 15:52] Philipp Deycke [Jboss encryption module and web frontend for TIM] |
en:software:tim:encryption_tim [2021/07/01 09:52] (current) |
||
|---|---|---|---|
| Line 77: | Line 77: | ||
| ====TIM Properties==== | ====TIM Properties==== | ||
| ----- | ----- | ||
| - | In tim.properties credentials can be encrpyted with the encoder or the console and replace plain text usernames and passwords. As an example the image shows setting and editing the superuser and client-administrator passwords: \\ | + | In //tim.properties// credentials can be encrpyted with the encoder or the console and replace plain text usernames and passwords. As an example the image shows setting and editing the superuser and client-administrator passwords: \\ |
| {{:en:software:tim:encryption_timproperties.png?400|}} | {{:en:software:tim:encryption_timproperties.png?400|}} | ||
| \\ | \\ | ||
| Line 83: | Line 83: | ||
| ====E-Mail Configuration==== | ====E-Mail Configuration==== | ||
| ----- | ----- | ||
| - | In the properties of the client unter the category mail server are the paramters SmtpUser and SmtpPassword.\\ | + | In the properties of the client unter the category //mail server// are the paramters //SmtpUser// and //SmtpPassword//.\\ |
| - | These credentials can be encrypted accordingly to the methods above and as shown in the example. {{ :en:software:tim:encryption_mailserver.png?400 |}} | + | These credentials can be encrypted accordingly to the methods above and as shown in the example. {{ :en:software:tim:encryption_mailserver.png?600 |}} |
| \\ | \\ | ||
| Line 90: | Line 90: | ||
| ----- | ----- | ||
| Actionhandler like HTTPRequestHandler or RunSqlScriptHandler use credentials that can be encrypted by said methods. The example shows the RunSqlScriptHandler where ${user} and ${pass} are passed on encrypted via smartform: | Actionhandler like HTTPRequestHandler or RunSqlScriptHandler use credentials that can be encrypted by said methods. The example shows the RunSqlScriptHandler where ${user} and ${pass} are passed on encrypted via smartform: | ||
| - | {{:en:software:tim:encryption_runsqlscripthandler2.png?600 |}}{{ :en:software:tim:encryption_runsqlscripthandler.png?800 |}} | + | {{:en:software:tim:encryption_runsqlscripthandler2.png?600 |}}{{ :en:software:tim:encryption_runsqlscripthandler.png?1000 |}} |
| \\ | \\ | ||
| \\ | \\ | ||
| Line 96: | Line 96: | ||
| ====Timer==== | ====Timer==== | ||
| ----- | ----- | ||
| - | Just like actionhandler TIM can encrypt nessesary credentials for timers and hide them from plain text. The example shows the Timer signalByMailReply: | + | Just like //actionhandler// TIM can encrypt nessesary credentials for //timer// as well and hide them from plain text. The example shows the Timer signalByMailReply: |
| - | {{ :en:software:tim:encryption_signal.png?1000 |}} | + | {{ :en:software:tim:encryption_signal.png |}} |
| \\ | \\ | ||
en/software/tim/encryption_tim.1529934743.txt.gz · Last modified: 2021/07/01 09:55 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: 2013 T!M Solutions GmbH
