Lasso and FMP containers

[notmyphorte]

We have several FMP 6 databases hosted with Point In Space which are accessible on the web via Lasso 5.

They have set a master username and password for us to use in Lasso Security, which we can use to query the databases and output the results to web.

However, so far we have mainly been using text fields and some value lists. We recently tried to serve up an image from a container, only to find it generates a login dialog (all other text field queries do not).

We are using LassoScript and setting a variable to Image_URL with an Inline search block.

The query itself works - it returns a path back, a unique identifier id and so forth - but it is this result which activates the login dialog.

Image_URL becomes:

/directory_path/filename.lasso?-database=DB_name&-table=cgi&-recordID=65&image=jpeg&-image

This may be correct, but without entering the username and password we can't tell (an we have tried entering our master Lasso username and password, to no avail).

We believe it is Lasso security configured incorrectly (as the Image_URL command does not allow you to specify a username and password like a normal LassoScript Inline query). The variable set to the value of Image_URL is being requested from the database and set within a LassoScript Inline search block - but when the page tries to server the image it generates the login dialog (and it makes sense why it does it for security reasons - but how do we get around it?)

Does Lasso security need reconfiguring to allow such use?

Many thanks for any light you can shed on this.

Tom.

[Anatoli]

Much better will be serving the raw images from images directory/folder by web server -- not Lasso -- and storing only the name/path of image in FM text field.

[notmyphorte]

Should have explained - we know paths are always better, but in this case containers are unavoidable - client will be copying images into the containers from a graphics program.

I know we could get them to save the image and then use FMP plugins to upload the images to the web server, but with the project time scale and budget they want a quick solution.

Using containers worked fine with ordinary CDML, but we think the hosting company has incorrect permissions set in Lasso Security which is why it won't serve images from the containers.

It's really more of a Lasso Security questions that a FileMaker, CDML or containers vs paths issue.

Using paths would fix it - but it would probably add 2 days on the project because of the extra functionality that requires for the client, whereas containers should work now if it weren't for the Lasso security issues.

[Anatoli]

You are right, maybe it is just the field permissions.