Re: OWC and Analysis Services (cross-post)
- From: craig_amtdatatechnologies@xxxxxxxxxxxxxx <craigamtdatatechnologiesdiscussionsmi@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 17 Jan 2007 12:18:02 -0800
Thanks for this info. I'll give it a whirl tommorow at work
The authentication was set up as Basic as people will be accessing this from
a completely different domain, but we'd still like some simple
username/password control over access to the cube.
"Jéjé" wrote:
ok, when the OLAP virtual folder is on a different server then SSAS himself.
AND if you use the NTLM authentication
then you suffer a kerberos delegation issue. (search the MS support site
for: kerberos IIS and you'll have some procedures)
if the /olap folder use the BASIC authentication you have to specify a
username / password in the connection string.
if the /olap folder use the ANONYMOUS access then the login used to reached
the SSAS server is the account used in the associated application pool or
the account specified behind the anonymous authorization (I'm not sure)
the kerberos issue is not applicable if the /OLSP folder is on the SSAS
server himself.
"craig_amtdatatechnologies@xxxxxxxxxxxxxx"
<craigamtdatatechnologiesdiscussionsmi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:163336C4-CA86-469E-A8CC-4C51BD8FF5A7@xxxxxxxxxxxxxxxx
To clarify as well, Server B has IIS configured with the /olap virtual
directory, and in the first instance, the PivotTable connection string is
set
to access this.
:)
"craig_amtdatatechnologies@xxxxxxxxxxxxxx" wrote:
Hi,
Thanks for the reply. I've set up the role and users as suggested. I've
managed to get the web-page with pivot table talking to AS 2005 in our
internal network ... have now hit difficulties with external access.
The setup is:-
Server A hosts AS 2005 and cube
Server B on same domain hosts web-page with the PivotTable control.
Server B has been setup in accordance with ....
-
http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx
I have change msmdpump.ini so that <ServerName/> references server A
(which
hosts a default instance) ... so the tag reads
<ServerName>MyServer</ServerName>
I've also tried ...
<ServerName>http://<servername>/olap/msmdpump.dll</ServerName>
No, clients accessing the web-page externally obviously will know nothing
about our internal server names and IP address, so the ConnectionString
in
the PivotTable control will need to reflect this.
As per the last comments in the above msdn article, I've set the data
source
in the connection string to:-
- Data Source=http://<external IP>/olap/msmdpump.dll
Presumambly the PivotTable control talks directly to the above address.
My connection string is currently ...
<x:ConnectionString>Provider=MSOLAP.3;Cache
Authentication=False;Integrated
Security=SSPI;Persist Security Info=True;Initial Catalog=SMMT_Cube;Data
Source=http://<ip>/olap/msmdpump.dll;Impersonation
Level=Impersonate;Mode=ReadWrite;Protection Level=Connect;Auto Synch
Period=20000;Default Isolation Mode=0;Default MDX Visual Mode=0;MDX
Compatibility=0;MDX Unique Name Style=0;Non Empty
Threshold=0;SQLQueryMode=Calculated;Safety Options=1;Secured Cell
Value=0;SQL
Compatibility=0;Compression Level=0;Real Time Olap=False;Packet
Size=4096</x:ConnectionString>
I've fiddled about with various settings here to, accoring to various
error
messages (of more or less use).
Also, client machines have XML, OLAP OLEDB 9.0, and OWC installed.
So basically, I'd be grateful to get help with configuring the setup
corretly.
To recap:-
Server A hosts AS 2005 - (also hosts and has IIS configured with
/olap/..)
Server B hosts web-page with pivote control
Client C (external IP) runs pivot control which needs to talk to A
via B
Thanks for looking at this again.
If you need more details (other than our passwords :)! ) let me know.
Craig
"Jéjé" wrote:
what is the XMLA virtual directory security?
do you allow anynomous access?
if yes, then create a role in your SSAS database with a member which is
the
account used behind the anonymous access of the virtual directory.
if you don't allow anonymous access then add the end user account in
the
membership list of the role.
"craig_amtdatatechnologies@xxxxxxxxxxxxxx"
<craigamtdatatechnologiesdiscussionsmi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:611353EB-A5FE-4005-91B0-160489D9E645@xxxxxxxxxxxxxxxx
Hi,
We've been asked to enable an external client to access a cube via
OWC.
The idea is that if they play about with the cube through the
PivotTable
control, this will enable them to define their requirements for a
reporting
system to sit on top of the cube.
I've read and implemented the contents of the following document:-
-
http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx
I've installed OWC and the SQL data access components on a test
machine,
and
have been trying to access the cube through a web-page hosting the
pivot
table control.
Data access across domains is enabled in IE
The error returned is "The query could not be processed: The HTTP
server
returned the following error: Forbidden."
Obviosuly some security setting somewhere needs to be tweaked ... but
which
one :/
Access to the web-page hosting the OWC control will be locked down by
IP
address.
Bearing all the above, what is the most straightforward means of
enabling
access via the OWC PivotTble control?
Thank you for help.
- References:
- Re: OWC and Analysis Services (cross-post)
- From: Jéjé
- Re: OWC and Analysis Services (cross-post)
- From: craig_amtdatatechnologies@discussions.mi
- Re: OWC and Analysis Services (cross-post)
- From: craig_amtdatatechnologies@discussions.mi
- Re: OWC and Analysis Services (cross-post)
- From: Jéjé
- Re: OWC and Analysis Services (cross-post)
- Prev by Date: Re: Processing Cubes
- Next by Date: Re: Newbie Question on Measures
- Previous by thread: Re: OWC and Analysis Services (cross-post)
- Next by thread: Re: Problems with SCOPE and EXCEPT()
- Index(es):
Relevant Pages
|
