Atlas App Services
239 results found
-
Client Side Field-level encryption for Realm Sync
Support client-side field-level encryption in MongoDB Realm.
https://docs.mongodb.com/manual/core/security-client-side-encryption/
https://docs.mongodb.com/manual/core/security-automatic-client-side-encryption/Basically, it would be nice if we could mark fields as being "sensitive" in the schemas, and Realm Sync would make sure to encrypt the fields before they are sent from the client app to the MongoDB Atlas database.
6 votes
Otso
responded
Here's an example on client side encryption with Realm Kotlin SDK on Android https://github.com/realm/realm-kotlin-samples/tree/main/AppServicesUsageSamples/apps/property-encryption
-
FTP Access to Realm Hosting
Uploading web apps into the hosting directory can be time consuming using only the ATLAS UI - specifically because the UI/UX does not support uploading entire folders. This means you have to re-create the folder structure, and upload specific files into specific folders rather than just uploading a single folder with all folders/subfolders.
This problem could be easily solved by providing FTP access to the "hosting" section.
1 vote -
Realm sessions
Could you please add a "remember me" or option for longer sessions on the Realm / Atlas Web UI?
Besides the annoying factor of daily/24h re-sign-in, a couple of times I lost function changes when working in a tab that was left open overnight and a save would fail due to a stale session.1 vote -
Atlas Realm deployments to Canadian Datacenter
We would like a deployment of Realm in a canadian datacenter either in AWS or Google Cloud.
1 vote -
Additional Filters to App Users Page
Add additional filtering capabilities to the "App Users" page. Currently you can only by "id". Im not sure if its due to our app setup but the "id" seems like a totally random generated id that is not associated to any data in our DB. It would be nice to filter based on name, createdTime, last login time, etc instead of just id
1 vote -
Add two factor authentication
It would be great to have an option for two factor authentication to increase security. Ideally this would be via authentication apps such as Microsoft Authenticator, email or SMS authentication would be viable too.
17 votes -
One-time scheduled triggers
At the moment, MongoDb offers the ability to schedule triggers periodically using Cron Jobs. It would be really handy if a user could schedule a trigger to run only once and execute a function as my use-case requires.
1 vote -
Support for dynamic Open Graph Protocol meta tags
Ability to whitelist certain IP addresses for social media crawlers and send them to a function that does server-side rendering of the index.html page to create open graph protocol (https://ogp.me/) meta tags for a dynamic link preview depending on what the link is. This specifically applies for single-page webapps.
1 vote -
More Granular Realm UI Permissions
At this time, the only permission that allows access to Realm is Project Owner; however, Project Owner grants permission to change a plethora of things inside Realm. In our case, we have testers who do not need the ability to change code. The testers only need to change Values and add users. Could a new permission class be created to support this?
18 votes -
Link Two Email Credentials
Should be able to link two or (preferably) more different email address credentials to 1 realm user.
Most obvious use case for this would be an app that has both a business domain, and a personal domain. The user can log in to their realm account with either their personal email addresses or their business email addresses.
1 vote -
Disable/Enable all triggers at once
It would be very useful to be able to disable/enable all triggers of realm application at once. It useful for instance when you restore data from backup or make some big changes, and it is not needed to run triggers on every change
1 vote -
Configure rate limit
It would be nice to be able to configure rate-limiting to prevent DDoS, scraping or unwanted requests that could highly increase the cost of MongoDB Realms
63 votes -
Increase RealmReturn Body Max Size
The maximum return body size of a realm webhook is 4MiB (4194304 bytes). That might seem enough for most applications but when dealing with massive amounts of data, e.g. timeseries data over years, that is a hard limitation.
It requires the client to make many more requests that would be necessary.In our special case we want to return one whole year worth of data per request to make things easier for our clients (currently they can get 3 months).
Given a 16MB Limit on a MongoDB Collection Document, this would seem like a sensable option for a limit if…
5 votesHi Marc – We have a ticket for this that’s near the top of the backlog and plan to increase the limit to 16MB in the near future.
-
1 vote
-
Add support for GitLab
As an alternative to using GitHub
5 votes -
Improve Realm Documentation for Various SDK Integrations
With existing examples and documentation about Realm SDK integrations was a bit confusing.
Example: React Native SDK - hard to find best example for offline first mobile app with realm (sync)
if we can have GitHub repo example integrations with minimal features for each SDK implementation it would really helpful for the community to find what they're looking for.
Contribution: communicate can contribute by giving an example for each or multiple feature implementation examples.
3 votes -
changeEvent cluster name
I want to be able to programmatically access the clusterName from change event or global variable for example:
changeEvent.ns.cluster = <CLUSTER/SERVICE name>
global.CLUSTER_NAMEI need this when I want to perform an update on same collection/document after the trigger, but i don't want to hardcode the clusterName - because i have multiple environments - each has its own cluster (dev/sandbox/prod etc...)
1 vote -
Realm roles in Atlas Projects
Currently we only have two roles available for Realm Users:
1. Project Owner
2. Project ReadOnly
Would be great to have more roles for Realm Users with the ability to give access to specific Realm App or give access to Realm only without giving access to the entire project. Something like Realm WriteRead and Realm ReadOnly roles
Thank you,
Anton15 votes -
easily manage single configuration file for different environments for ci/cd
simply support environment variables expansion in database name or table name
this way a single configuration folder can be used to configure multiple realm apps
but each realm app will use a different database/table so the data is separated.
an official mongodb example code from a blog post about this topic uses this expansion but talking with support they said it is not supported and that the example code is wrong.2 votes -
External Dependencies Management (npm)
A lot of 3rd party libraries don't work, even ubiquitous ones like Joi. We upload zipped node_modules and all we get are errors.
Devs now spend time building simplified versions of these libraries so we don't get the full benefit of a using a battle-tested library and also waste time writing functions that we shouldn't need to write. This is a huge pain and a productivity killer.
15 votes
- Don't see your idea?