Florin Lungu’s Post

How to Effectively Manage Unique Identifiers at Scale: From GUIDs to Snowflake IDs and Other Modern Solutions What Are Unique Identifiers? 🪪 Unique identifiers (UIDs) are crucial components in software engineering and data management. They serve as distinct references for entities within a system and ensure that each item – whether a database record, a user... Read mode on following blog post!

Transform your data like a pro with inbound-only custom casts! 🔄 This technique secures info when it's saved, perfect for hashing passwords. Check out the article from the community!

Monday Moment; data collected, and managed, by staff appointed by - and funded by - your income-, sales-, property, et al, taxes - the gob'mint you elected to represent you, should not require an upcharge. Especially that the data queried to display those web-forms is a) likely added by the public, keying in their data to the web form, and b) already in a dataset which can easily be queried and returned in specified format, with no additional effort (other than a DBA, perhaps, to manage security of public keys). You can harvest the format (using api / other syntax-rules) directly into your data-warehouse. System-crash prevention is easily handled with limiting fetch size (### records) and looping fetch until all records are returned in format of user-choice.

What Sets the History Plugin for IdentityIQ Apart from Access History? The History Plugin and Access History both track identity and role changes, but they cater to different needs. 🔹 Focus & Data Integration Access History focuses on changes to roles, entitlements, and capabilities. In contrast, the History Plugin integrates data from all IIQ sources and its own change detection—even allowing customers to "bring their own" audit event data for deeper insights. 🔹 Maintenance & Updates Access History changes require a patch or version upgrade (such as the coming improvements in IIQ 8.5). The History Plugin is continuously updated and supports IIQ versions from 7.2 to the latest. Upgrade whenever you're ready! 🔹 Scan Triggers Both tools scan for changes to identities and accounts. The History Plugin offers flexible scan options (scheduled tasks or background service), whereas Access History uses a fixed job start date for all changes. 🔹 Storage & Reporting The History Plugin stores events as IIQ Audit Events, making them easy to access and analyze with SQL queries, while Access History uses JSON format, which can be more challenging to work with for attribute-level changes. 🔹 User Interface The History Plugin’s compact UI allows for quicker access to key data with a customizable timeline, while Access History’s UI requires more scrolling and screen space. Want to dive deeper? Check out this blog by Devin Rosenbauer on the History Plugin: 👉 https://lnkd.in/emnniD46

🚀 Understanding COMMIT, ROLLBACK, and SAVEPOINT in Transactions 💡 In the world of databases, managing transactions is crucial for ensuring data integrity and consistency. Three important concepts help us do that: COMMIT, ROLLBACK, and SAVEPOINT. Let's break them down: 🔹 COMMIT: Think of this as "saving your work." When you commit a transaction, you're making all changes permanent and visible to others. Once a commit is done, there's no turning back—those changes are stored in the database forever! ✔️ 🔹 ROLLBACK: On the other hand, a rollback acts like an "undo" button. If something goes wrong or you change your mind, you can rollback the transaction, and the database will revert to its previous state before the transaction started. ❌ It’s a safeguard to ensure no incomplete or incorrect data is saved. 🔹 SAVEPOINT: A savepoint allows you to set a "checkpoint" within a transaction. You can rollback to this specific point without canceling the entire transaction. It gives you more granular control when handling complex operations. Think of it as saving a draft at multiple stages in a long document! 📝 In a nutshell: COMMIT = Make changes permanent. ROLLBACK = Undo all changes since the last commit. SAVEPOINT = Create a checkpoint to roll back to within a transaction. Using these wisely can help ensure robust and error-free database operations. ⚙️ #DataManagement #Database #Transactions #SQL #Commit #Rollback #Savepoint #DataIntegrity #Learning #TechTips

Server-side API responses vary with methods. GET retrieves data, POST submits new data, PUT updates existing data, DELETE removes data. Choose the right method to manipulate resources effectively and securely. 200 OK ✅ #Success #GET #ResourceFound The request has succeeded. The server found and returned the requested resource. 201 Created 🎉 #Success #POST #ResourceCreated The request has been fulfilled, and a new resource has been created. 204 No Content 🚫📄 #Success #DELETE #NoContent The server successfully processed the request, but there is no content to return. 400 Bad Request ❌📝 #ClientError #BadRequest The server cannot process the request due to client error, such as malformed syntax or invalid parameters. 401 Unauthorized 🔒❌ #ClientError #Unauthorized The request has not been applied because it lacks valid authentication credentials for the target resource. 403 Forbidden 🚫🔒 #ClientError #Forbidden The server understood the request but refuses to authorize it. 404 Not Found ❓🔍 #ClientError #NotFound The server cannot find the requested resource. 405 Method Not Allowed 🚫✋ #ClientError #MethodNotAllowed The method specified in the request is not allowed for the resource identified by the request URI. 409 Conflict ⚔️ #ClientError #Conflict The request could not be completed due to a conflict with the current state of the target resource. 500 Internal Server Error 🛠️🔥 #ServerError #InternalServerError The server encountered an unexpected condition that prevented it from fulfilling the request.

Take a deep dive into the background of the company behind it You can get a fair idea about whether a Mac email backup tool is worthy of your trust by leafing over its company’s background. See that the software development team has been in existence for several years and whether the company has a valid address. Further, you can also try to understand the intent behind making the tool available and what are the benefits you will get if you choose it for Mac mail backup. Well begun is half the work done and if you have developed enough confidence about the company’s background, you must verify if the tool is in sync with the current technology. https://lnkd.in/dvMtwQ3h

📦 How to not lose your SysReptor data. SysReptor encrypts data at rest by default. This affects sensitive data in the database and file uploads (like images). 🔑 This data is encrypted using symmetric keys stored in the web application configuration (app.env). 🔥 If you back up your Docker volumes but not the encryption keys, you won't be able to restore your data. 📄 Also back up your app.env to not lose your encryption keys. 🦖 The built-in backup feature in SysReptor Professional decrypts all data before putting it into the backup. You can, however, specify a public key, with which the backup can be encrypted.

Do not limit the length of the passwords! Every once in a while I encounter a web site where the length of the password is limited. Usually to 8 characters. This is really scary. I am trying to figure out why would any developer want to limit the length of the password you use. I can think of two explanations. One is that someone thought that "it would be hard for you to remember a longer password so we limit it to 8 characters". Is this patronizing? Where would this come from? The other, much worse is that they have allocated a given size of space (e.g. 8 characters) in the database where they store the passwords and they want to make sure yours will also fit in. This is really scary as this would indicated that they store the password as you typed in. In clear text. That's a huge security hole as that means anyone who can see the content of the database will have all the passwords. So for example if the admins store a backup of the database on some place that less secure than the original database server then someone might be able to access that. The correct way to store passwords is to use some kind of a strong hashing algorithm. The nice feature of all the hashing algorithms is that they take any arbitrary long string and convert it to a fixed length string. For example sha256 will give you a 256 bit (32 bytes) long string. Regardless of the length of the input. So your password can be 10 characters or 20, after the conversion it will be 32 bytes long and that's what the developer needs to store in the database. Maybe with a few extra characters. So the developers can fix the allocated place in the database and they can be sure that regardless of the length of the real password they will only need to store the expected number of bytes.

I use this approach to mark a database record as deleted in 99% of cases.