Console One + Ldap

[cmptech]

Good Afternoon ,

I would like to acces since a workstation with formativ runtime without novell client , hen they’re configuring with protocol Ldap !
And when i try to connect to the server i have this error : ldap_simple_bind_s(49)

In console one ,
Config the Server Ldap with adresse IP and port 389 with Groupwise !

But there are somethiong to do in Ldap Server and Object ?!

Thank for your help !
Tech

how to configure the server for the protocol Ldap

Topic

[cmptech]

Good Afternoon,

Do you think, another method exist ?!
No use Novell Client and LDAP, but use Local Applets only , and in path select a map from your server ?! . Default , your applets must be encoded before !.

Thank for your help !
Tech !

[Support 2]

Yes, you could store your applets in a shared network folder location. For Formativ Runtime users, you do need to Flexalock the open source applets, otherwise they will not operate.

With respect to LDAP, the LDAP Error 49 is LDAP_INVALID_CREDENTIALS: This indicates that during a bind operation one of the following occurred:

– The client passed either an incorrect DN or password.
– The password is incorrect because it has expired, intruder detection has locked the account, or some other similar reason.

I could not find any information in our support history which would assist you further.

Kind Regards,

Advansys Support

[cmptech]

Good Morning,

thank for your answer !

Applets need to be Flexalock instead of Encoded ?!
What’s the difference ?!.

When you do it formativ add the extension “app_encoded.vbf” or “app_flexalock.vbf”

Example :
Before Encoding or Flexalocking !
A applet “app1.vbf” call a another “app2.vbf”

After Encodind or Flexalocking !
these applets become app1_encoded.vbf and app2_encoded.vbf
The first applet could call the second ?!

thank for your help !
Tech

[Support 3]

The following section copied from the Developers Guide which explain the difference between Flexalock and Encoded Applets:

quote:

---

Flexalock Applets can be partially or fully encrypted. Flexalock Applets are useful when you wish to lock down part of an Applet’s source code, leaving key constants exposed that others can modify as required. In addition, Formativ Studio and Creator can be used to modify a Flexalock Applet’s client integrations and convert an open source Applet to a Flexalock Applet. To ensure maximum security and end-user flexibility, Applets written for commercial distribution should be converted to the Flexalock format.

Encoded Applets are fully encrypted. The source code and client integrations are completely locked down and cannot be modified by anyone except the developer who has access to the original open source Applet. Formativ Studio and Formativ Creator can convert an open source Applet to an Encoded Applet. Due to the introduction of the more flexible Flexalock Applet format, the Encoded Applet format is now used rarely.

---

Hope this helps.

Regards,
Advansys Support

[Author]

Replies