Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Author
    Replies
  • in reply to: Enterprise Access via Trusted API not working #9328
    stevecrye
    Participant

      Hi,

      We had already tried specifying the TCP/IP info for our post offices.

      However, while looking at the systems.xml, I noticed that it listed the path to the Primary Domain as K:pridom, and realized that for the low-power users, I had map rooted K: directly to \episd15mail6pridom. I changed that mapping to match what I use when logged in as an Admin-equivalent . i.e.
      map k:=episd15/mail6:

      I deleted the previous trusted keys, edited the systems.xml and cleaned out the previous GW systems, and re-created the trusted keys.

      I shutdown the laptop, and restarted it, logged in via Client 32 (C32 in Novell slang 😉 ) as a low-power user, but into windows as the same local user. This time we did not get the “(not available)” after EPISD-ADMIN, and after about 30 seconds could see the users in the post offices.

      It now works as expected.

      We will be very glad when the new version that does not require Write permissions to the Primary Domain folder is available.

      Thanks,

      Steve

      Steve

      in reply to: Enterprise Access via Trusted API not working #9325
      stevecrye
      Participant

        Hi,

        Well, it tried harder but still failed. Please see this link for the details:
        http://www.episd.org/Steve_Files/archive2goProblems2.doc

        I also sent the email with the GW system tester results and the .xml files.

        Thanks,

        Steve

        in reply to: Enterprise Access via Trusted API not working #9330
        stevecrye
        Participant

          Hi,

          Thanks for the prompt and detailed reply.

          Yes, when logged in with full admin rights we can use the archive creator with no problems in Enterprise mode. We are not currently using Reveal, although we did run it for 30 days about 6 months ago in trial mode. We deleted the Reveal trusted app via Console One.

          I’ll test it in the morning with a non-admin user that has RWF rights to the pridom folder, and let you know ASAP the results of that test. If it still fails we will send the diag info as requested.

          However, granting the Write right makes us nervous – does that not expose the entire system to the danger of someone accidentally opening up any of the critical files such as wpdomain.db and altering them? (We are using clerks to do the archiving).

          A couple more questions about the procedure for setting up the trusted app key on a clerks workstation. We have been logging in via C32 on that workstation as an Admin equivalent, creating the trusted app key, and then having the clerk login with his usesrid to perform the archiving. Is that the correct method? Also, where exactly is the trusted key stored on the workstation, and where is the object in the tree?

          Thanks,

          Steve

        Viewing 3 replies - 1 through 3 (of 3 total)