Recent content by mattbbpl

  1. Signing Users Out When They Close the Browser

    For whatever reason, this is not ending the session in OAM. The OAM session remains orphaned.
  2. Signing Users Out When They Close the Browser

    That's unfortunate. Thanks for your reply, though. It's good to have confirmation. There are procedural workarounds such as leaving an additional tab open (even to something basic like Google's main page) so that the session isn't lost on the client when the screen is closed, but users see...
  3. Signing Users Out When They Close the Browser

    We are running JD Edwards EnterpriseOne 9.1, and we have SSO/WNA successfully enabled using Oracle Access Manager. This all works great. When users launch JDE initially it will automatically log them in using their desktop credentials, and if they launch another tab and navigate to JDE the new...
  4. IE8 crashing after windows patch installation (released 11/10/15)

    I feel his pain, though. We rolled out IE11 just a few months ago. Before that, we were only authorized to use IE8 as well. The limitation caused all kinds of headaches. Truth be told, IE11 still causes headaches - just fewer of them.
  5. Validating QSoft's Claims: Role Limit, Performance, 2 Role Per User Strategy

    The problem with one role per user is just logistical, not technical. It's easier to create 1 role for each employee type (i.e. plant manager, forklift operator, accountant, HR representative, etc.) and 1 role for each location than create a role for each employee type/location combination.
  6. Validating QSoft's Claims: Role Limit, Performance, 2 Role Per User Strategy

    Thanks for your reply. This is exactly what I was looking for in this regard, I was just hoping for something more official. It looks like I'll have to demonstrate in a sandbox environment once it's available to do so.
  7. Validating QSoft's Claims: Role Limit, Performance, 2 Role Per User Strategy

    Regarding performance, I'm seeing references in knowledge base articles for other Oracle products stating loose comments about, "it all depends on the OR comments generated". These products use a similar inclusive/exclusive row security model as JDE, filtering out records by appending WHERE...
  8. Validating QSoft's Claims: Role Limit, Performance, 2 Role Per User Strategy

    I found this document in the knowledge base (A 255 Character Limit Appears To Be Evident On Assigning Roles To Workflow Step (Doc ID 1501014.1))...
  9. Validating QSoft's Claims: Role Limit, Performance, 2 Role Per User Strategy

    We are using Qsoft to manage JDE 9.1. We're currently using a very rudimentary security setup in a proof of concept system, but we're looking at setting up a more robust "finalized" security structure in Dev and, later, production. Researching, I found the following two blog posts from QSoft...
  10. Multiple Email Addresses in TO EMAIL field

    I think we might be going off into the rough, here. Assuming he's correct on the conditions he states he's seeing, it shouldn't have anything to do with separators and the like. Presumably (and hopefully he can confirm this through a test), he's able to send email messages to multiple valid...
  11. JDE E1 9.1: SSO/WNA on the Thick Client

    Good point. I'm used to seeing the choice between a thin and fat client as irrelevant in terms of functionality (i.e. the only reason to choose a fat client over a thin client is to distribute the business logic onto users' machines, thereby decreasing the load on the centralized servers -...
  12. I hate this new format.

    Just to chime in, it is a little confusing, particularly when combined with the fact that posts, responses aren't posted immediately. It's very easy to go on auto-pilot and click the wrong button, then later wonder whether it was submitted at all, even. This is coming from a new member with...
  13. JDE E1 9.1: SSO/WNA on the Thick Client

    Thanks guys. Getting confirmation on the current version's capabilities in this regard has been an immense help.
  14. JDE E1 9.1: SSO/WNA on the Thick Client

    Thanks for the suggestions. I don't have direct control over the software purchases, so I can't decide to use Everest's solution, cowboy style. It sounds like I'll have to propose a hard decision, though - Either we purchase a third party tool, we ban/limit fat client use, or we make an...
  15. JDE E1 9.1: SSO/WNA on the Thick Client

    We're working through our security requirements and designs for the first phase of a JDE E1 installation. In this particular case, we were discussing our SSO (Single Sign On) and WNA (Windows Native Authentication) design, whereby we would like a user who is logged into the Active Directory...
Top