Windows Media Services 9 publishing point security config help
- From: DanJBunting <DanJBunting@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 6 Nov 2009 01:23:01 -0800
I need some ideas on how to configure a Windows Media Services publishing
point on an ingress server that is password protected, so that an encoder
ingress stream to the publishing point requires a username and password. At
the same time we need to have a relay publishing point configured on a
seperate egress server, which is not password protected and therefore open
for all users to access, which relays the stream from the ingress server
publishing point that we password protected. The servers in question are all
part of a domain.
I have got a configuration like this working in some sense but there appear
to be drawbacks in my solution. On the ingress server I create the PUSH
publishing point which is password protected with WMS Negotiate
Authentication and WMS Publishing Points ACL authorization enabled. I am
however unable to then set up an egress server publishing point that is open
to all users which can access that ingress mount point directly, presumably
due to the fact that the ingress publishing point requires authentication
which the egress publishing point does not carry. To work around this I need
to configure an additional publishing point on the ingress server with no
authentication protection. This additional publishing point references a wsx
playlist file and in the wsx playlist file I have an lpp:// local publishing
point reference to the original ingress PUSH publishing point. I can then
configure my egress server to point at the new ingress publishing point and
the relay works as required.
However, as mentioned there is a drawback in using this method. If an
encoder is connected to the publishing point and it is stopped and restarted
in a short time period (e.g. to change encoder settings) the stream does not
become available again via the egress servers for a very long time. As far
as I can figure out from testing, this behaviour is due to the fact that the
second ingress publishing point which references the wsx playlist gets in a
state where it has not flushed out the previous instance of the stream before
the encoder was stopped and therefore can not accept the newly started
stream. This obviously causes problems. I have tested with using
WMNoDataTimeout and WMNoDataTimeout2 elements in the wsx playlist to attempt
to flush the previous stream but this does not seem to help.
My question therefore (if you have understood my ramblings so far) is does
anyone have any different/better ways of achieveing what I require, or
perhaps recognises the issue that I am seeing in the way that I am currently
doing it and has a workaround to that?
Many thanks.
.
- Prev by Date: RE: Windows Server 2008 RC and Media Services
- Next by Date: RE: Can't Connect to Windows Media Streaming From the Internet only L
- Previous by thread: RE: Windows Server 2008 RC and Media Services
- Next by thread: RE: Can't Connect to Windows Media Streaming From the Internet only L
- Index(es):
Relevant Pages
|
