f058c266d2
Add username and display name form fields on account setup
2016-04-05 09:27:32 +02:00
e0114c87ac
Also update the user record when username and email is sent
2016-04-05 09:27:32 +02:00
c98275000b
Optionally support username and email in password setter route
2016-04-05 09:27:32 +02:00
553509c462
implement installation of app bundle
2016-04-04 23:03:13 -07:00
306bef96b4
remove dead DNS_IN_SYNC
2016-04-04 22:14:05 -07:00
497eaea65e
bump expiry to 60 mins
2016-04-04 16:02:13 -07:00
8aacc503a6
Revert "getRestoreUrl now uses caas restore api"
...
This reverts commit f9fc9325a8995dc0a9cb1dfcf22fb27eca697a89.
For now, we can simply assume that caas is s3 based.
2016-04-04 15:57:32 -07:00
ec160fe45f
make getBackupUrl return id as well
2016-04-04 12:45:09 -07:00
82c74e6787
add backupdb tests
2016-04-04 12:41:17 -07:00
bbff195863
rename filename to id
2016-04-04 12:20:56 -07:00
e528dbcfc0
creationTime is redundant
2016-04-04 12:13:54 -07:00
0467e80c71
remove unused require
2016-04-04 12:13:25 -07:00
c9ef0056e0
rename getSignedUploadUrl to getBackupUrl
2016-04-04 12:01:47 -07:00
efb228cf5e
getRestoreUrl now uses caas restore api
2016-04-04 11:57:29 -07:00
af700827c5
info is not passed anymore
2016-04-04 11:44:24 -07:00
3135783fe3
rename getSignedDownloadUrl to getRestoreUrl
2016-04-04 11:43:56 -07:00
496f530b9f
sessionToken is required in credentials (when signing)
2016-04-04 11:23:38 -07:00
fcfd1dceac
Deliver the resetToken when an invite was sent
2016-04-04 18:41:51 +02:00
d839f0b762
remove redundant session token
2016-04-03 23:23:23 -07:00
16a65fb185
drop configJson
...
The initial idea was to store exactly where the backups are stored.
But this only causes problems for migrations where the bucket might
change and clones where the prefix (box.id) changes.
Thus, it's best to leave the url creation to the caas side. (That
has to be done in another change)
2016-04-03 22:55:08 -07:00
c236072c4c
add comment
2016-04-02 18:04:58 -07:00
5d92cff638
backup config.json first because tarball takes lot of time and leads to token expiration
2016-04-02 18:01:49 -07:00
1b539b8d22
upload as binary
2016-04-02 17:58:10 -07:00
a21a913f34
delete snapshot on failure path
2016-04-02 17:57:15 -07:00
357f6f0552
use same region as what we uploaded to
2016-04-02 13:32:14 -07:00
b16aa4c007
check for region as well
2016-04-02 13:31:12 -07:00
29077abf7c
pass back the changeId
2016-04-01 23:21:10 -07:00
42fc2d446c
do not set the session_token header
...
this seems to be part of url now in signature v4
2016-04-01 13:26:25 -07:00
3ea2070cdb
pass filename (it is not part of the config!)
2016-03-31 09:53:56 -07:00
fc11484b51
pick region from apiConfig if present
2016-03-31 09:48:38 -07:00
b4ddfa94cc
rename to apiConfig
2016-03-31 09:48:13 -07:00
9e7ae1a4f7
we really need a better linter
2016-03-31 09:38:40 -07:00
d27159275b
pick region as well
2016-03-31 09:34:57 -07:00
6c2ae756f1
fix usage of backupInfo
2016-03-31 09:23:41 -07:00
92e4433dff
make backupdb.get return app backups
2016-03-31 09:12:12 -07:00
c4cbd9f4e4
mailer: check for the correct SPF record
2016-03-31 08:44:31 -07:00
f413afb835
Support email login in simple auth
2016-03-31 16:59:44 +02:00
915c37a72f
Add tests for displayName change
2016-03-31 16:24:28 +02:00
1ddb3a58da
Also send displayName in simpleAuth
2016-03-31 16:24:28 +02:00
a4aa5bbc59
fix linting
2016-03-31 00:51:38 -07:00
39cc5d07d1
use the backupdb config to determine bucket and prefix
2016-03-31 00:50:56 -07:00
df39384056
do not save backup secrets in database
2016-03-30 23:39:48 -07:00
47c5cad239
fix typo
2016-03-30 17:06:50 -07:00
c097651a88
store backup configuration as part of backups table
2016-03-30 15:04:39 -07:00
9e8179a235
up link is relative
2016-03-29 14:02:53 -07:00
2c4cf0a505
Download intermediate cert following the 'up' Link
2016-03-29 12:51:05 -07:00
ae8a371597
add adminFqdn in the spf record
...
For custom domains, we do not set the A record for the naked domain
(because the user might be using it for his own). This means that
a:domain.com will not work.
The solution is to simply use the admin domain.
2016-03-27 23:05:29 -07:00
ead076bd9f
add MAIL_SMTP_PASSWORD
2016-03-25 23:14:09 -07:00
f8c683f451
Disallow updating an app with mismatching manifest id
...
Story so far:
1. App installed from store. appStoreId is set to manifest.id.
2. User installed a custom built app with a custom manifest.id using cloudron install --app <id>. The appStoreId is still set.
3. When we make a new release, it overrides the users install.
The fix (for now) is:
1. Do not allow mismatching ids to start with.
2. When forced, it is allowed but appStoreId is cleared so as to not get any auto updates.
This leaves the user vulnerable to 'cloudron uninstall' simply autoselecting this new app.
For this, they have to simply disable CLI mode for now.
There is also a corner case where:
1. Dev installs from app store
2. Dev compiles from source and updates on top of app store install with --app <id>
3. Dev find out that his installation has auto-updated the next day.
2016-03-25 11:46:25 -07:00
b56bc08e9a
Allow to use email and username for ldap bind
2016-03-24 21:03:04 +01:00
Johannes Zellner