Jump to content

Juan David Gil

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Juan David Gil

  • Rank
    member
  • Birthday 01/27/1979

Profile Information

  • Title
    Product Specialist
  • Industry
    Commercial Healthcare
  • Gender
    Male
  • Location
    Colombia

Contact Methods

  • Skype
    jdgw.gilmedica

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Wim... I am latin, always say hi. The check mark is the one that says "Use Secure Sockets Layer (SSL)" on the picture. I know you have repeated here a few times, but I do understand, eventually. Thanks for the patience.
  2. Are you sure? This is a surprise to me! To be honest, I always thought that the server was the gateway between FMS clients and the AD. I have to admit I don't know much about this. Then, what does that check mark do on that 'Directory Service' do?. I am sure the EventId started happening since I installed FMS and the server that flags that event is only authenticating FMS requests, but never realized that clients do not use FMS as a passthrough to the AD. So, If I understand, the clients read the data from the FMS and then they directly challenge the AD server? To answer your question: I am working FMP on a Mac client bound to an AD. Following your valuable insight, I will see if only using Windows clients that are bound to the AD will also spawn the EventId on the server. Thanks
  3. Juan David Gil

    Push Only also Pulls

    I don't know if this is still active or relevant. But I guess your problem is that for both devices you are telling them to ES_PUSH, and hence, both PUSH... With your experience in mind, I will use them one PUSH and the other PULL.
  4. Thanks again Wim. Right. You are right. But notice that my problem is that when the FMS goes to check the AD, it does so without any encryption and in plain text. Thats why I would like it to be secure. The kind of alarms that it raises are the EventId: 2887 on the server administrator window. It specifies that clients are being authenticated against the AD without any encryption.
  5. Thanks Wim, I will answer accordingly I am referring to the authentication of user names against an Active Directory. You set up a server, and must give them FQDN a port and a type of encryption. For instance, the mail server get all accounts with user names @domain.com and authenticate them internally against an AD domain server with @domain.local accounts using SSL with a self signed certificate from the server... but its encrypted! I use with them Port: 636 using LDAPS protocol. And thats it. It is a member of the domain, but it has no role at all as a server for any of the Active Directory services. Done! Indeed it works! But using non encrypted connection, thus, raising alarms in the DC. You activate it in the admin console, under the 'Database Server' --> 'Directory Service' --> 'Use Secure Sockets Layer'. AD is listening on 686 for the SSL connection. I too wish to know this.
  6. Excellent video. I had to bleed throughout my learning, but this did straight out some kinks. It did not talk about using SSL to authenticate agains Active Directory
  7. I have an Active Directory for user authentication for our FMP users. I, however, must use unencrypted connection because otherwise it does not work. I have tried and tested the same parameters on other solutions to authenticate against AD, and they work, but with FMS, it works only unencrypted. I read the Manual, it says that I must use a certificate, but my domain is '.local' and I don't understand why it needs a supported certificate for this matter. I did install a certificate for FMP so in order to avoid the annoying web direct security statement. All said, I have a Windows 2008 R2 level domain, with 3 servers to authenticate against. A dedicated FMS windows 2008 r2 server that belongs to the domain. What must I do?
  8. Thank you. Steven taught me what I had wrong. Thank you so much for your input. This solved the deal.
  9. Using a Filemaker Server 14 trial in a Windows 2008 Server R2 environment with Active Directory on another Server. The Domain is a Windows 2008 server level. Clients vary from Windows 7 to MacOSX El Capitan to FileMaker 14 Go, but all of them are not showing the save password or with a functional SSO, whilst the FileMaker 13 version do work. I don't know if I have provided the information you need.
  10. I was using FMP 13 and FMS 13 for most of our work and testing. However, once we upgraded to FMP 14, our SSO or saving passwords to keychain/other password managers, are no longer show or work. We are using FMS on a local domain and FMP to access it too.
×

Important Information

By using this site, you agree to our Terms of Use.