Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.

AFCS Unsecure username and password can view while tampering

Avatar

Level 1
  • We noticed that when we tamper data we are seeing the username and password. We hope this will solve ASAP
  • How to limit messages in Chat history, I need to delete old messages, it must only leave 50 messages.
4 Replies

Avatar

Former Community Member

Hi ghost,

From where and how are you tampering the data? The client? If so, are you logging in with a developer username and password? It's absolutely not recommended that you embed your developer credentials in a deployed application - it's fine during development time, but not with public facing apps. Could you describe more of what you're seeing?

  thanks

  nigel

Avatar

Level 2

Yes, i also notice that when i used the tamper data of firefox plugin.. the account username and password shows the post data.,, this is the part of my code

          con = new ConnectSession();
            var auth:AdobeHSAuthenticator = new AdobeHSAuthenticator();
            auth.userName = usern;
            auth.password = pwd;
            con.roomURL = room;
            con.authenticator  = auth;
            con.addEventListener(SessionEvent.SYNCHRONIZATION_CHANGE,onSyncs);
            con.login();

Avatar

Former Community Member

Hi Guys,

Again, I'd like to point out that you SHOULD NOT BE DEPLOYING APPS WITH

YOUR DEVELOPER CREDENTIALS EMBEDDED IN THE SWF. Please check out section 6.4

of the Developer Guide PDF - while you're building your app, it's necessary

to use developer credentials, but as soon as you want it to be

public-facing, you should move on to either anonymous (guest) authentication

or external authentication. You can also listen to the video tutorials,

which make this clear as well.

Even without TamperData, it would be just as easy to decompile your client

SWF and steal the username and password there.

If you follow the authentication models described in the developer guide

for deploying, you shouldn't run into any situations where anyone can steal

your developer credentials.

thanks

nigel