The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Calling .aspx pages in saleslogix webclient
Posted: 03 May 06 9:48 AM
|
fiogf49gjkf0d Hello friends I am using slx 6.2.3 web and SQL 2000. Is it possible to do the customization in ASP.NET, if yes then will it still maintain all the logs for the user.
Also can I call another sites login page from Saleslogix Web and pass the username and the passwod directly from slx web to my site so that the user does not need to login again.
Thanx |
|
|
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 03 May 06 6:40 PM
|
fiogf49gjkf0d Yes you can build ASP.NET pages and use them in the web client - IMO it's the *only* way to do SLX web development
Anyway, you just need to make sure the ASP.NET pages just use the SLX provider to perform any updates and etc so you can make sure things are still good and sync.
As far as passing the login values to bypass the login screen, you sure can. Here's some HTML you could use for a simple login screen to provide your own login details and bypass the login screen:
<html> <head> <title>SalesLogix Login</title> <script language="Javascript" src="http://YOURSLXWEBSERVER:1025/slxweb/jscript/default.js"></script> </head>
<body> <form name="mainform" language="JScript" onsubmit="GetTimeZoneInfo();" method="post" action="http://YOURSLXWEBSERVER:1025/scripts/slxweb.dll/login">
<input type="hidden" name="nextpage" value="mainpage"> <input type="hidden" name="tz_info">
User:<br><input type="text" name="user"><br> Password:<br><input type="password" name="password"><br> <br> <input type="submit" name="submit" value="Log in to SalesLogix">
</form> </body> </html>
One thing you'll notice is that we are referencing a Javascript file used by the web client. The GetTimeZoneInfo function called onSubmit is in that js file. You could add a value to the tz_info hidden field yourself if you wanted, just look at the function to see what is needed (and array of values is created and spit out as a string to the value of the tz_info field). But I think it is just easier to reference what is already there and use it.
Good luck. |
|
|
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 03 May 06 7:37 PM
|
fiogf49gjkf0d Basically, with bypassing the login screen, my point was that you basically just have to post 4 values 'user', 'password', 'nextpage', and 'tz_info' to slxweb.dll/login and all is well (i just wanted to mention that because you could just write some code to do that without an actual login form)
Know what I mean? |
|
|
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 03 May 06 11:56 PM
|
fiogf49gjkf0d Don't forget about authentication. Don't make the mistake of thinking that only SalesLogix Web Client pages will call your ASP.Net pages.
For example, do not hardcode your ASP pages to use the ADMIN login. This is just a caution if you had not thought about it.
Also, I am not sure what you mean about "maintain all the logs for the user". If you are worried about synchronization then Ryan's recommendation to use the SLX OLEDB provider is a must. If that is not what you are asking about, please elaborate.
I agree with Ryan that ASP.Net is nicer to code in. I absolutely LOVE visual studio. But sometimes it is easier to use the infrastructure provided. Displaying a datagrid of child records in a tab under the account detail doesnt warrant introducing ASP.Net IMHO. If you are doing mass customizations then you are already covering your ASP.Net investment .
Timmus |
|
|
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 04 May 06 1:49 AM
|
viagra weed erowid viagra weed strain fiogf49gjkf0d Thanks Guys, How can we send the authentecation information like Usernema and Password or Session id to the newly built Asp.net page that is called from SLX and then get the info sent to the asp.net page authenticated by SLX Server.
Thanks, Kirti |
|
|
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 04 May 06 2:05 AM
|
benadryl and pregnancy category benadryl and pregnancy fiogf49gjkf0d I guess that is my point, Kirti: YOU have to figure out what authentication scheme is acceptable to your organization. SalesLogix does not provide an authentication scheme for ASP.Net.
One idea is to use a caching mechanism for storing username and password and then to use the OLEDB provider to test those credentials on each and every ASP.Net page.
The problem is that this suggestion is full of holes: is the caching secure? What about encryption? What about enforcing strong passwords? etc.
Maybe someone else is willing to outline a security infrastructure for you but Sage will not, nor is it my expertise to recommend a way to secure your ASP.Net solutions. This is definitely a cop out.
Maybe someone else will step up and recommend an approach that they are willing to be accountable for. When it comes to security, academic pursuits just dont cut it.
Timmus |
|
|
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 04 May 06 10:51 AM
|
fiogf49gjkf0d Timmus does have some good points, but I have to say that I despise working in the web client. I avoid it whenever possible - but I do agree that you need to choose the right tool for the job (but for most cases for me that is VS )
As far as authentication, here's what I do. First of all, I place the connection values using the ADMIN user into a config file. All connections are made using the ADMIN's credentials (this does not mean we ignore the current user's security, read on). Then, when you integrate your ASP.NET pages into the web client, make sure to also pass the current USERID along to the page as well. This is an easy enough task since the SLX web client makes that easily available to you. Your link to your page (whether as the source of a frame in a frameset, or as a link that launches a new window) would look like this at a minimum:
<#SYS name=htmlpath>/CustomPages/MyPage.aspx?userid=<#SYS name=theuserid>
And chances are you'll also need to pass in other values as well, to give it context, and you can easily do that too - like an accountid for example:
<#SYS name=htmlpath>/CustomPages/MyPage.aspx?userid=<#SYS name=theuserid>&accid=<#F name=accid>
Now, once you have the USERID of the current user, in any connections in your ASP.NET pages, you'll simply impersonate that user. You'll need to first make a connecton (as ADMIN) to get the user's login name from the USERID, then add IMPERSONATE=username to the extended properties of the connection string to impersonate that user (so you'll have that user's security, etc)
The great thing about using ASP.NET for SLX web development is that if you do it enough (or just plan to) then you can build up a library of tools to make the development go far faster than if you were to do it inside the infrastructure provided with the SLX web client (can you tell I'm not a fan? ) |
|
|
| |
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 04 May 06 1:13 PM
|
fiogf49gjkf0d Ah, now I see what you are getting at. All I ever do is check the page referrer to make sure it came from a page in the web client (or check the frameset it is a part of). But really, we're talking about something like a tab deep inside the web client (that looks just like the rest of it). It would take some real digging for a user to find that they can just open that url and pass it some userid or something. Not to say that security isn't important, but I just figure as long as the page was called from some other page in the web client (and not just called from typing the page url in on the address bar) then that's about as safe as check as any. Sure the referrer can be spoofed by someone who knows enough, but it's not like that would be the only hole in the SLX web client |
|
|
| |
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 04 May 06 8:48 PM
|
fiogf49gjkf0d I never worked with SLX Web, but did it supports Windows Authentication just like the Client Version. If the answer is yes, then you can use the same authentication method in ASP.NET application, and retain the same credentials. But I'm guessing that the answer is no..
Does SLX Web allow catching event on client connect/diconnect like DBOpen scripts in the client version? If the answer is yes, then we probably can create some kind of authentication ticket (combination of a key, username and IP address), that can be used as a credential in our ASP.NEt Application. But I'm guessing taht the answer is no..
Dhany |
|
|
|
Re: Calling .aspx pages in saleslogix webclient
Posted: 05 May 06 1:42 AM
|
fiogf49gjkf0d 1. No, there is no Windows authentication in the web client. It is not impossible, or even very difficult, but there is no stock solution provided by Sage. 2. There is no matching "dbOpen" event in the web.
Your guessing is good
Timmus |
|
|
|