One of the most enjoyable challenges during the development process was ensuring the PDF documents are temper proof (sealed). Traditionally, some companies charge exorbitant fees, up to $10,000 for a 1-year certificate.
However, through meticulous research, we discovered a three-year certificate for a fraction of the cost, like $600. It offers the same level of functionality.
I had to contact every company from Adobe Approved Trust List: https://helpx.adobe.com/acrobat/kb/approved-trust-list2.html
To set up the necessary Hardware Security Module (HSM), we opted for Google HSM, which costs just a few bucks a month.
One of my ideas what to create Atlassian plugin that would allow to use custom domain.
I did some PoC. With heavy http proxing/rewriting it would be somehow doable but too fragile. I have skipped that.
Basically all of this is matter of Atlassian priority. If most of clients can accept current state then why bother?
It is good market, there are niche needs. Most of work is web development not rocket science.
Actually plugins for Jira / Confluence is something well done by Atlassian.
They can not create single solution for all, but with plugins? It is close.
> File name extension. This is a very common one. "cgi", even ".html" is something which will change. You may not be using HTML for that page in 20 years time, but you might want today's links to it to still be valid. The canonical way of making links to the W3C site doesn't use the extension.(how?)
Imagine, you work in bigCorp. You have company email address: [email protected]
bigCorp pays for your access to SaaS service.
You switch jobs, your email is revoked/removed. You can not log in anymore.
If there was no 2FA via email - you still can access service with email+password in case they failed to remove your access to specific service.
If all services use 2FA via email - bigCorp has less access problems.
That is also partly related with SAML/SSO lack of "sign off".