Showing posts with label clear. Show all posts
Showing posts with label clear. Show all posts

Sunday, March 25, 2012

Authentication, windows or custom

I have read most of the threads regarding form authentication as well as the suggested articles. Unfortunately I am not clear if I need to do custom security or stay with windows authentication

I would like to access a specific report using a URL so that all the features and funcionalty of the report is available to the user. There are to many users and reports to assign and maintain individual users and/or groups to a specific report.

Our users would access the report from either a windows or web application having already passed security. They would have a button to press to obtain the report. We would prefer to pass a specific userid to report services at this point that is authorized to view the report.

Can this be done without switching to custom security? To use form authentication must you switch to custom security? Would impersonation work?Hi,

If you go with Windows Authentication, then you can retrieve the Windows UserId from the Thread class - Thread.CurrentPrincipal.Identity.Name

Regards,
Vikram

Tuesday, March 20, 2012

Authentication

Hi,
I would like to configure a SOAP Endpoint on SQLServer 2005 as
AUTHENTICATION = (DIGEST) (.. PORTS = (CLEAR) ...), but when I do this, even
the IE can't connect anymore. Has anybody experience with this
authentication-method ?
The intention is to connect a small device, which only speaks TCP/IP to the
SQL Server. Or are ther any other possibilities to to this ?
Thanks,
SoerenHi Sren,
Just a guess, but are you running SQL Server on Windows XP SP2? The version
of IIS on this OS can't share port 80. So, if this is the case, run either
the HTTP Endpoint or IIS on a different ports. In HTTP Endpoint, its just a
parameter in the PORTS keyword.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Sren Rose" <rose@.inray.de> wrote in message
news:eTvULM5iGHA.1640@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I would like to configure a SOAP Endpoint on SQLServer 2005 as
> AUTHENTICATION = (DIGEST) (.. PORTS = (CLEAR) ...), but when I do this,
> even
> the IE can't connect anymore. Has anybody experience with this
> authentication-method ?
> The intention is to connect a small device, which only speaks TCP/IP to
> the
> SQL Server. Or are ther any other possibilities to to this ?
> Thanks,
> Soeren
>|||Hi Bob,
I'm running Win2003 Server, so thats not the problem, but I figured out what
the problem was: I have to create a domain and use a User from the domain. I
tried it with an local user an this faild. This is documented on the MS
Website too:
"The credentials sent as part of a digest authentication over HTTP must be
mapped to a valid Windows domain account. Local user accounts are not
supported for Windows-based digest authentication. "
Now it works :-)
Thanks,
Soeren
"Bob Beauchemin" <bobb_no_spam@.SQLskills.com> schrieb im Newsbeitrag
news:#JQRkB#iGHA.1204@.TK2MSFTNGP02.phx.gbl...
> Hi Sren,
> Just a guess, but are you running SQL Server on Windows XP SP2? The
version
> of IIS on this OS can't share port 80. So, if this is the case, run either
> the HTTP Endpoint or IIS on a different ports. In HTTP Endpoint, its just
a
> parameter in the PORTS keyword.
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb
>
> "Sren Rose" <rose@.inray.de> wrote in message
> news:eTvULM5iGHA.1640@.TK2MSFTNGP02.phx.gbl...
>sql

Saturday, February 25, 2012

Attribute Relationships, Related Attributes, Uniqueness

I haven't see a clear example of how to setup the following for efficient aggregations:

Example 1:

If I have a Hierarchy like:

Year->Month->Day

Its clear how to setup the attribute relationships as long as the Month members are all unique. Can I somehow include an Attribute like WeekendIndicator? Weekend certainly isn't unique, but it would seem there should be a way to roll this up and include it in the attribute relationships.

Example 2:

In many of my dimensions, I have Hierarchies whose Name member is not unique, but there is an Id value that is unique. I want to build the relationships using the Ids since I know the aggregations will be good...the problem is, that a program querying the data would use the IDs, but a person writing a report would want to use the Name attributes. Is there a way to link the two together so that the non-unique name members are tied to the Id fields. The User Defined Hierarchy define on names works fine from a UI perspective, but I want to make sure I have aggregations as well.

For example, if I have a Campaign dimension, and users frequently want to navigate these for rollups:

Account -> MarketingProgram->MarketingCampaign

The fact is an Order

The Program and Campaign names can be anything, but their IDs are enforced to be unique. How do I manage these together?

Example 3:

And finally, if I want to do rollups with the following types of attributes

AccountStatus->AccountCategory->Account

I can't build an attribute relationship for this since Account Category does not imply Account Status since all accounts of a certain category are not guaranteed to be within an Account Status. How do I efficiently build aggregations for this type of hierarchy? The User Defined Hierarchy allows the customer to navigate it, but the aggregations don't allow it.

Thanks for any insight!

Example 1

Create a new attribute WeekeendIndicator and use it to filter the time dimension.

Example 2

One way to resolve this by adding the name and id in a view or Data Source View as a calculated value, e.g.
Market Development Fund (1)
Market Development Fund (2)
Market Development Fund (3)

Example 3

If the hierarchy is enforced (or a strong hierarchy) such as the time dimension, then aggregations can roll up.

Hope this helps.

|||

That's a solution , but not quite what I want to do.

Example 1 -> Is there a way to pre-aggregate this information with attribute relationships?

Example 2 -> I know I can generate unique names, but is there a way to "pair" attributes together so I can leverage the Ids for the aggregation but see the names elsewhere

Example 3 -> The issue is the hierarchy is not enforced, so is there no option for attribute relationships of any kind, is there another way I should model this?