Opened 16 years ago

Closed 13 years ago

#105 closed enhancement (fixed)

Allow username and password to be passed via url, like ajax viewer

Reported by: andrewd Owned by: madair
Priority: P2 Milestone: 2.3
Component: MapGuide Version: SVN
Severity: Minor Keywords:
Cc: Browser: All
External ID: Operating System: All
state: Analysis Requested

Description

It would be nice if the Fusion viewer behaved like the other viewers when it comes to security. If we could pass usernames and passwords via the URL like we can for the ajax viewer, it would be a great improvement.

It's nice to be able to have passwords on layouts, but as the same time, there are also cases where you just want to be able to access those protected layouts without the user needing to login (for example, they've already logged into a portal site of some sort). I realize this could all be done by making a session and passing that, but for those of us who are using Studio or Maestro solely, then that's not a viable option.

Change History (8)

comment:1 by pagameba, 16 years ago

Milestone: 1.12.0
state: NewAnalysis Requested

reevaluate for 2.0

comment:2 by madair, 14 years ago

Milestone: 2.02.1

look into this for 2.1

comment:3 by madair, 14 years ago

Milestone: 2.12.2

comment:4 by madair, 14 years ago

Status: newassigned

can you clarify the requirement here please? If there is a username/password combo passed in via query parameters, do you want user/pass to be passed along to all requests to the MG server? What is the best way to show the issue and test the solution?

comment:5 by andrewd, 14 years ago

It's been a long time since I submitted this (2 years now), but I'll do my best...Here's how I recall things - The ajax viewer lets you log in via a url by using the "USERNAME=" and "PASSWORD=" args. For example, "http://server/mapguide/mapviewerajax/?WEBLAYOUT=Library://test/MainLayout.WebLayout&USERNAME=Administrator&PASSWORD=whatever". I have no idea what the mechanics of that are, but it's been that way since the start. I know that 2 years ago, this did not work if you were using a fusion layout. Who knows now - I've had to stay away from fusion because of this and a few other issues...but odds are, it's still the same as it was.

Does that help?

comment:6 by madair, 14 years ago

Milestone: 2.22.3

i'll need better requirements/use case description to fix this, deferring to 2.3

comment:7 by andrewd, 14 years ago

I'm afraid that I've been as descriptive as I can be. The basics are simple - the Fusion viewer doesn't (or at least didn't, when I reported this 2 years ago) behave like the other viewers (DWF and AJAX) when it comes to passing usernames and passwords in a url. If it's by choice, then I for one would disagree with the choice, but so be it. If it's an oversight / bug, then it should really be fixed sometime.

comment:8 by jng, 13 years ago

Resolution: fixed
Status: assignedclosed

Fixed with r2434

Note: See TracTickets for help on using tickets.