Security Through Insanity
-
Me: "Can I have access to the test version of the [important banking system] app, you know so we can test the migration?"
'Manager': "Okay. I will request you access to the production system."
Me: "No! I in no way need or want acccess to production."
'Manager': "No, the way the [roll you own!] access management system works, you need access to production before you can have access to test."
Me: "....[creates new dailywtf account to share this 'gem'.]"
-
Concise, disturbing and highly WTFey.
Rating:
-
Me: "Can I have access to the test version of the [important banking system] app, you know so we can test the migration?"
'Manager': "Okay. I will request you access to the production system."
Me: "No! I in no way need or want acccess to production."
'Manager': "No, the way the [roll you own!] access management system works, you need access to production before you can have access to test."
Me: "....[creates new dailywtf account to share this 'gem'.]"
Unfortunate, but true. That is most ldaps do not have test mode. So first create your user id on ldap that is production. Then same user id get used every where else. THere is also a simple thing about database refresh. Test is typically refreshed from prod. So you need to exist in prod, before coming into test. Typical system admins just do not want to get into the trouble of creating you on test and only to make your user id vanish after a prod refresh.
I am not saying this is the only way to do it, but this is how things are done only.
-
I read this WTF with the understanding that there would be naked ladies whom Gary-sue protagonist would get to romance. However, once the article was delivered, I found only your standard management WTF-ery. I was left mildly intrigued, but the lack of wish-fulfillment fanservice is frustrating. Would not click again.
Rating:
-
naked ladies
I've heard that there are websites that can cater to this specific need.
Filed under: I've never seen one though...
-
That is most ldaps do not have test mode.
That is why one has multiple users. One for day-to-day work, one for admin tasks and when dealing with applications with LDAP/domain security at least one test user.
-
..snip... reasonable argument how to organize test environments ...snip...
Or, you can just use the production database for testing as well.
This is from a new food ordering site. And no, it isn't a temporary mistake. They've been visible for months.
-
-
@Luhmann said:
That is why one has multiple users.
Or, like, a separate test system.
Accessible through the live system, via the QA system...
-
@boomzilla said:
Or, like, a separate test system.
Accessible through the live system, via the QA system...
Obviously.
-
Or, you can just use the production database for testing as well.
That is what one bank in Southern area of California near San Deigo is doing. I do not wish to name it as they can trace that to me.
-
That is what one bank in Southern area of California near San Deigo is doing. I do not wish to name it as they can trace that to me.
Great...
-
Or, you can just use the production database for testing as well.
-
Pull sucks, push blowspush sucks, pull blows indeed.
-
That is why one has multiple users. One for day-to-day work, one for admin tasks and when dealing with applications with LDAP/domain security at least one test user.
You can also use one LDAP domain to drive multiple configurations by giving different users different attributes and including them as required in the relevant lookups. It's one of the saner ways to map access control rôles…
-
My first thought upon the title was something related to Discourse, XSS and self-escaping.
-
My first thought upon the title was something related to Discourse, XSS and self-escaping.
Oh, self-escaping! I thought you wrote self-scraping for a moment, and that DC was using regular expressions to convert the baked posts into a form it could display…
-
You mean it doesn't?
